Beyond MVCBeyond MVCBeyond MVC 03/08/2004 11:21 PM Although the Model-View-Controller design has proven itself throughout the years to be an appropriate and beneficial pattern for modeling user-interface components, its use in designing distributed servlet infrastructures has led to very unfortunate results. Among these are the advancement of unwieldy, inflexible architectures that are incapable of being quickly altered to support the ever-changing demands of the technological and economic environment. The only time I've ever felt comfortable with MVC was when i was learning Smalltalk, because that was the natural way to code user interfaces for that environment. I have never been impressed with the way MVC has been retrofit for web user interfaces, as it appears unnatural in the web context. There are many simpler web metaphors that are viable (For example, see Rasmus' Ad ding Structure example or Smarty). MVC is very much in the over-designed style of J2EE. The DataSource, Action, Workflow objects the author suggests looks pretty similar to what my company (we've been doing workflow since 1997) does internally for our more complicated user interface scenarios, though i would need a closer look to be sure. Interesting, provocative, and definitely worth further study.
This is a GrokNews Entry: (what is grok?)Beyond MVCGrok Headline matches for Beyond MVCGrok Description matches for Beyond MVC GrokA matches for Beyond MVC Beyond MVCThe following phrases have been identified by the grok system as matching this entry: |
Also check out: |