Its somewhat of a chicken and egg problem. The controller interacts with
the model in response to user actions on the view, the view formats and
displays data it querys from the controller, and the model holds the actual
data that the controller querys/updates. There is no real "main" peice as
they can all be modified/repaced independently. And MVC is used all over
the liturature so its accepted (just like TCP/IP should really be IP/TCP
based on packing order, but if you say the latter people will look at you
funny hehe) and people will know what you are talking about.
Just my 2 cents,
Amir
-----Original Message-----
From: Johan Fredriksson [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 05, 2001 6:25 AM
To: Orion-Interest
Subject: Re: JSP vs Servlet MVC - CMV
I've seen the abbreviation MVC on a lot of places, but shouldn't it be
CMV
for Controller / Model / View
where Controller receives a request, handles it using model and displays it
using view....?
Not important to me, just wondered... =)
//Johan
----- Original Message -----
From: "Fyffe Carl" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Friday, January 05, 2001 9:07 AM
Subject: JSP vs Servlet
> I went to jollem.com and read the CMP Primer. Good read. But it got me
> thinking about a topic that concerns most people that are in large
> development groups. Seperation of code and html. Proper MVC calls for
the
> code to be in the controller while there is little code in the view
portion
> of the application. This allows the designers to design and the coders to
> code.
>
> Were the rules broken for convience or has a new methodology taken over?
It
> seems to me that the CMP Primer would have been easier to read and
> understand if MVC had been used.
>
> This one short coming can easily overlooked to find a gem of an article.
> Are there other primers of jollem.com's caliber? What are some useful
URL's
> that you guys used to get started.
>
> --Carl
>
