I've heard a lot of great things about using XML in combination with JSP to
make it easier to change the presentation for other languages(Spanish,
German, etc.) and protocols (e.g. WAP/WML). I know very little about XML
but from what I have read it seems like it would have very significant
run-time overhead. Is this true? A lot of people seem to be using it (or
recommending it) so maybe it's not as bad as I think.... Or maybe the
assumption is that if you have a web-server farm it doesn't really matter if
the load-capacity of each server is diminished by the xml-translation
overhead (as long as it doesn't put more load on the back-end resources,
which it probably wouldn't) since it's cheap and easy to toss a few more
front-end (web/servlet/jsp/EJB-client) servers in the farm.
I'm in the early stages of developing a very large, (hopefully) highly
scalable web site and I'm trying to decide if it's worth it to go down the
XML path or if it's just going to be another heavyweight API that'll take
time to learn and lots of cpu time to run (as if servlets, JSP, EJB, HTML,
JavaScript, OODB, etc weren't enough).
Any comments/recommendations would be appreciated.
I've included at the bottom of this message a snippet from
www.OrionServer.com which mentions using XML to handle HTML and WML.
Brien Voorhees
-----------------------------------------------------------------
Our WAP strategy is basically to make dynamic content being as easy to do
for both web and wap clients as for just one of them. The strategy is to
have JSP:s (talking to EJB:s) that produce XML documents. Then, a
client-dependent XSL is used to transform the XML into either HMTL or WML.
All this is automated. What the developer has to do is this: Write an XML
JSP (And any beans, ejbs, etc. in the system) or just an XML file (for
static content) and write two XSL files (one for html, one for wml). Orion
will automatically determine whether the user is using a normal web browser
or a wap client and return the correct document. Our goal is simply to
transparently bring the J2EE platform to wap clients as well as normal
browsers.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
