Hi Jason:
Jason says...
> I prefer that, just as I prefer how template engines enforce the separation.
I don't understand this. Maybe you expand on it on your paper but I do
not recall it - and yes, I'll eventually find the time to read it more
carefully than the first time, sorry.
But, how does a template engine "enforce" the separation? If the
template language is sufficiently expressive it can be abused. If it is
not, then it is not sufficiently expressive. And it is kind of hard to
be strict about these things. For example, in the JSP space, it would
be possible to say: you can only use this set of custom tags, and, who
knows, this may come out from an XML-based syntax for JSPs (if we do
them) since one could ask for validation, etc. [[NOTE! I'm not saing
this will happen, or not - I am just exploring an argument :-)]] but
short of this I have no really good ideas.
Even Java can be (and is) abused. And what is an abuse in one case it is
totally valid in another. Engineering is all about trade-offs.
Anyhow, how does a template engine enforce this separation?
- eduard/o
___________________________________________________________________________
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
