> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Paul McCallick > Sent: Saturday, January 22, 2011 2:27 PM > To: [email protected] > Subject: The reality of web mvc > > I've been thinking about how most web apps these days do some serious > JavaScript backflips, and how that sort of violates the mvc pattern. > With all of that magic happening at the view layer, you're sort of > forced to make some processing decisions that never hit the contr > > Thoughts, strategies?l
The problem stems from the fact that MVC is a UI pattern, and web apps are services delivering messages, not UI. A true MVC platform would be all JavaScript. MVC just so happens to very closely match the resource-oriented nature of the web so that it makes it difficult to catch the slight mismatch. So what you really need to do is segregate your service (web app) from your UI (JavaScript). Then you'll see the clean divisions and be able to do some MVC with JavaScript. Check out Sammy.js, among others. Ryan -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" 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/altnetseattle?hl=en.
