This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: A general question


> 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?

If you're developing for an Intranet and you can ensure that you can specify
the browser then go ahead and develop for a specific browser.  

If you're developing for the Internet in general and you need to ensure that
you content is accessible by the widest audience possible then you have to
do the transform on the server side (along with many other things you might
also want to otherwise do client side).  The cost of any extra hardware
needed on the server side needs to be part of your business model: we are
trying to make our content available to audience "x", therefore it will cost
us "y" dollars to do so.  If you can't afford "y", your business model is
broken...



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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]