Re: Best Practice - Modules to build a web application
- From: Mark Clements <mark.clementsREMOVETHIS@xxxxxxxxxx>
- Date: Sun, 18 Mar 2007 20:53:30 +0100
Joseph Brenner wrote:
Joe Blower <motiv8x{AT}top25web.com> writes: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.
- 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).
YMMV :)
Mark
.
- References:
- Re: Best Practice - Modules to build a web application
- From: Joseph Brenner
- Re: Best Practice - Modules to build a web application
- Prev by Date: Re: help with module naming: filehandle-tie for size-limited/rotating logfile
- Next by Date: Re: Proposal Database::Initialize::Postgresql (naming okay?)
- Previous by thread: Re: Best Practice - Modules to build a web application
- Next by thread: Proposal Database::Initialize::Postgresql (naming okay?)
- Index(es):