"Robert A. Crawford" wrote:
> A template system separates the HTML/formatting from the
> logic....
Hi,
Thanks for the feedback, everyone. It'd be interesting to make a taxonomy of
web content generation ideas, and implementations of those ideas.
For example, the way that these HTML template systems have been described
makes it sound like they're competitors to the idea of XML+XSL.
I wonder how these two approaches compare? An advantage of HTML might be that
"anyone" can do HTML layout, but writing XSL is much more like programming.
On the other hand, a servlet producing XML (which gets transformed by XSL),
seems like it has a more clearly defined function; it would construct an XML
doc of a known type. It also seems like passing XML around would "scale"
better in a design sense. You've got a formal description of a particular
important abstraction in your system.
But in "typical" web/scripting/app-writing scenarios, this kind of design
formality might be a drawback.
Comments?
- Robb
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
