Re: A general question

[TP]
>
> > 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?
>

You might be able to cache the stylesheets once they were compiled, so that
they don't have to be rebuilt each time they are asked for.  You might be
able to transform any static pages to html beforehand and serve them with no
overhead that way, if you have any static pages or even quasi-static ones
(say, ones that changed once a day at predictable times).  You might be able
to use a proxy server to cache transformed files if it turns out that you
are serving the same transformed content frequently.

You might combine any or all of these techniques with some of the other
suggestions.  Of course, none of this is a easy as lettign the browser do
the transform, but you can't count on that as you have already pointed out.

Cheers,

Tom P


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