Re: The "Presentation" Layer

Yes, thats the correct term used for it.

It's a general SE principle which does not only apply to MVC of course but to all parts of a software system. It's about avoiding "spaghetti code". For example the M layer could also be divided in parts that only "know" about clients and another part that only knows about products. The only things these parts know about (besides their core competency so to speak) is the interface of the other parts. Like the "client" module knows about the "orders" interface to retrieve it's associated orders.

MVC is an important principle, but it's only a specific application of the generic "separation of concerns" principle applied to the overall system which applies nicely to almost every system with a user interface.

Anyway, it's off topic, and there is lots of information available on the internets ;)

Date: Thu, 17 Jul 2008 07:29:28 -0500
From: aaronbartell@xxxxxxxxx
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] The "Presentation" Layer

There is code that only "knows" about presentation and nothing else; code

that only "knows" about navigation and code that only "knows" about
business.

Good point John. That reminded me of the phrase "Separation Of Concerns"
which is defined on wikipedia.com if anyone wants to read up on it.


http://en.wikipedia.org/wiki/Separation_of_concern

Aaron Bartell
http://mowyourlawn.com
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

_________________________________________________________________
Probeer Live Search: de zoekmachine van de makers van MSN!
http://www.live.com/?searchOnly=true