(I'm crossed posting to the JSP mailing list because there's a similar
discussion raging over there)
Justin Wells wrote:
> In fact, JSP only really provides you with support for a model versus
> view+controller separation--it takes a template system to realize the
> full value of the model/view/controller design.
It's interesting to note that in the world of GUI toolkits, where MVC has its
origins, there has been a concerted move from full separation between model,
view, and controller to a merging of the view and controller components. For
example, Borland's OWL and Java's Swing both implement a Model/View+Controller
architecture instead of Model/View/Controller. If I'm not mistaken, I believe
that even VisualWorks Smalltalk, which is widely regarded the standard bearer
for MVC, eventually moved to a Model/View+Controller architecture.
In theory, full separation between model, view, and controller seems preferable
to an architecture that merges views and controllers. However, in practice a
clean separation between views and controllers is unworkable because views and
controllers are typically tightly coupled. For example, it's difficult to
develop generic controllers that are not to some degree intimately familiar with
some type of view.
So, if historical precedence is significant, it would seem that JSP's design is
preferable over that provided by a template system.
david
P.S. You can read more about the history of Swing's Model/View+Controller
architecture at
http://java.sun.com/products/jfc/tsc/archive/what_is_arch/swing-arch/swing-arch.html
___________________________________________________________________________
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
