To clarify:
It is bad practice to mix the data access, domain, and presentation
layers of an application. MVC. Superficially, this means we don't want
to have SQL queries in a template file, and we don't want HTML mixed in
with code to calculate e.g., category rankings. What you want is
separate layers to 1. Get the data and pass it into the domain, 2.
Transform the data and pass it to the presentation, and 3. Present the
data. (The data itself is inert-- it's just what the layers are
shuttling around).
On Fri, 2008-04-18 at 12:38 -0500, Jess Planck wrote:
> Yup, but I can never understand that argument for the Web.
>
> The final output sent the browser is code, although some people don't
> consider html, css, and javascript code. So here we are with data that
> has been pushed into a code blender on the server and we hand it to a
> client that will then stir it with a ( sometimes very dirty / ugly)
> code stick in the browser.
>
> Ahhh... refreshing!
>
> Jess
>
> On Apr 18, 2008, at 12:12 PM, Ron Johnson wrote:
>
> > Isn't it bad practice to mingle code and data????
>
> ___________________
> Nolug mailing list
> nolug@nolug.org
___________________
Nolug mailing list
nolug@nolug.org
Received on 04/18/08
This archive was generated by hypermail 2.2.0 : 12/19/08 EST