On Feb 15, 2011, at 10:43 , Andrey Popp wrote:
> MV vs. MVC is just about terminology. But C in MVC is the most "dirty" place
> -- all code that has no excuse to be in M or V is placed in C. So, I think
> it's better to keep my controllers clean and slim, so that's how I like MV
> paradigm :-).
Gentlefolk,
As I am new to your community, please indulge me some ignorance and
naïveté with respect to your platform.
The problem with MVC for web apps is pretty simple. MVC was designed
for a tightly bound, native code application. The web just isn't that kind of
environment. The web is more of a VbC--sCM (view-browser controller--server
controller-model). I know the acronym is cumbersome; I prefer MRVC --
Model-REST--View-Controller. This architecture is part of impetus to build REST
App Servers. New Twitter is a great public example of this architecture. New
Twitter exclusively uses the API to get it's info. It does appear to be helping
their scaling issues.
Anon,
Andrew
____________________________________
Andrew W. Donoho
Donoho Design Group, L.L.C.
[email protected], +1 (512) 750-7596
"To take no detours from the high road of reason and social responsibility."
-- Marcus Aurelius
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
