RE: [xsl] A general question

Subject: RE: [xsl] A general question
From: "Brinkman, Theodore" <Theodore.Brinkman@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 18 Feb 2002 14:46:47 -0500
I'd actually recommend detecting which browser you're serving content to and
making the decision based on that.  (get hit by NS 4 = serve the processed
xml, get hit by NS 6 = serve the 'raw' xml).  But that's just my opinion.

	- Theo

-----Original Message-----
From: TP [mailto:tpass001@xxxxxxxxxxx]
Sent: Monday, February 18, 2002 2:39 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] A general question


> It would make it browser independent, but I'm not sure it would make it
> faster (more work being done on the server, so unless you have a very
> number of people using your web site or a very beefy server it would
> make it slower).

So, is it not a good idea to parse on the back end if by doing so, we lose
performance. What do developers generally do? Do they use front-end parsing
or back-end parsing? I know that there are a few book authors on this list.
What would you recommend?



> Whatever you do depends on what server-side language you use.  If you use
> ASP, then plugging in MSXML is pretty easy (although I won't touch ASP
> personally so I can't tell you what to do).  If you have access to a J2EE
> server, then you can write your own Servlet that integrates with your
> favorite Java processor (Xalan, Saxon, etc.).  You should also check out
> Cocoon (, which is a server explicitly
> for doing XSLT transformations.  PHP I believe has its own XSLT plugin as
> well.
> On Monday 18 February 2002 09:24, TP wrote:
> > Hi,
> >
> > I am working on an servlet based application that was designed by
> > else. What we do is that we send xml data over to the browser and we
> > on the browsers xsl processor (msxml) to parse the xml into viewable
> > what this has done is that we are now very much browser dependant, such
> > that our application cannot be viewed on any other browser other than
> >
> > What we want to do is, of course, avoid this. What I was told is that if
> > used my application server to parse my xml instead of the browser, this
> > would make the process faster and browser independant. i.e., parse the
> > on the server side rather than the client.
> >
> > I am a newbie on this and need some direction about where I should start
> > studying about this. Can someone please guide me on this.
> >
> > Thanks in advance.
> >
> > TP.
> >
> >  XSL-List info and archive:
> --
> Peter Davis
> The Official Colorado State Vegetable is now the "state legislator".
>  XSL-List info and archive:

 XSL-List info and archive:

 XSL-List info and archive:

Current Thread