Re: Best Practice - Modules to build a web application

Joe Blower writes:

>> - Support of Model View Controller Conecpt (MVC)
>
> not sure what this is.

Seperation of html (the "View") from code is mostly what this means.

It's never been that clear to me where the break is supposed to
be between "Model" and "Controller", but I would guess this
largely just means database and code; though you might take
it to mean SQL and perl, which would explain all of the many and
various object-relational-mappers (which actually prevent you
from using the database relationally, as far as I can tell).

Re: Best Practice - Modules to build a web application

Joseph Brenner wrote:
> Joe Blower writes:
>
>>> - Support of Model View Controller Conecpt (MVC)
>> not sure what this is.
>
> Seperation of html (the "View") from code is mostly what this means.
>
> It's never been that clear to me where the break is supposed to
> be between "Model" and "Controller", but I would guess this
> largely just means database and code; though you might take
> it to mean SQL and perl, which would explain all of the many and
> various object-relational-mappers (which actually prevent you
> from using the database relationally, as far as I can tell).
>
>
My interpretation is that the model contains the business logic and
interaction with the database, whereas the controller marshals user
input and invokes methods on the model accordingly before returning the
view to the user.

YMMV :)


Mark