Re: MVC philosopy question
Daniele Futtorovic wrote:
On 29.01.2008 16:36, David Sharp allegedly wrote:
My apologies. I should have been more clear. My question pertains
to Web Applications.
Dave
Sorry for the precocious post -- bloody crtl-enter.
Web applications are somewhat of a special case wrt MVC, due to the
network barrier and stateless HTTP. In web applications, with tools like
JavaScript et al., you effectively transfer some part of the controlling
to the client side. For that controlling to be more effective and
powerful, you end up backing it with parts of the model -- on the client
side, and thus necessarily bound to a page (if we discount cookies).
I think that's where your confusion arises from. You don't have that
situation in desktop applications.
In its full panoply of glory the MVC pattern admits of multiple controllers.
That "backing bean" of which you spoke is called the "controller" in Java
Server Faces (JSF).
The notion of having one or multiple *models* is sort of like asking if that
big bowl of Jello (r) in the fridge is one Jello, versus when you serve it to
the family in 4.5 bowls, is that 4.5 Jellos?
How you cut it is arbitrary - choose a taxonomy that supports development and
maintenance the best.
--
Lew