Actually, if your GUI is a web page then it is often quite easy to separate
the View from the Controller: just divide the page into a View frame and a
Control frame that has a form with control elements. The form gets
submitted to a servlet, and, in a reasonably well designed system, the
servlet will do some sort of generic dispatch to a back-end system. It
seems that Justin Wells thinks of such a servlet as a Controller... which
just shows that, in a distributed system, we have to spend some time
figuring out what we mean by all those terms.
> -----Original Message-----
> From: David Geary [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 09, 1999 3:30 PM
> Subject: Re: JSP vs Servlets?
>
>
> (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/swin
g-arch/swing-arch.html
===========================================================================
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
