Design Element
Comment on "Separation of Model and View Web Frameworks"
by Scott Stevenson — Sep 10
@Matt: Check out Seems to offer an awesome way to bridge the gap between client-side Javascript and services (as in SOA) on the server-side

I read through this site quite a bit, and it's interesting in that it seems to be a different approach. That is, it treats the server as more of a services-centric data vendor and tries to do all of the formatting on the client side.

I don't necessarily disagree with this design, but I couldn't find any stand-out examples on the site that really sold me on the framework. The Overview page is a little bit vague and cites a number of things covered by other popular solutions.

In general, I want to keep my web app environment as "stock" as possible so that I don't have to watch over each piece and play mediator between them. This framework introduces another layer to the stack and a separate syntax. I'm willing to take that on if there's a clear advantage in doing so, but like I said, nothing jumped out at me.

For people that want to have more of the smarts on the client side, it's an interesting option. For me personally, I'd like some specific examples of what problems it solves, rather than just a dicussion of what service/message-oriented design mean in the abstract sense.
Back to "Separation of Model and View Web Frameworks"
Design Element

Copyright © Scott Stevenson 2004-2015