RE: A general question

There are four possible drawbacks to client-side transformation (please
don't call it parsing!):

- if the XML file is large in comparison with the generated HTML, it can use
more bandwidth and latency
- it doesn't work on all browsers
- it's insecure if the XML contains data you don't want everyone to see
- it can reduce the number of hits that you measure on your server!

If none of these factors are relevant, client-side transformation has many
advantages.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of TP
> Sent: 18 February 2002 19:39
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  A general question
>
>
> Hi,
>
> > 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
> small
> > number of people using your web site or a very beefy server it would
> actually
> > 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?
>
> Thanks,
>
> TP.
>
> >
> > 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 (http://xml.apache.org/cocoon/), which is a server explicitly
> designed
> > 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
> someone
> > > else. What we do is that we send xml data over to the
> browser and we
> rely
> > > on the browsers xsl processor (msxml) to parse the xml
> into viewable
> html.
> > > 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
> IE.
> > >
> > > What we want to do is, of course, avoid this. What I was
> told is that if
> I
> > > 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
> xml
> > > 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:
http://www.mulberrytech.com/xsl/xsl-list
>
> --
> Peter Davis
> The Official Colorado State Vegetable is now the "state legislator".
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>
>

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list