Everyone understand what MVC does and why, well probably not, but they think they do. I'm thinking about a MACRO MVC. Where the mashup is the Controller and the View is the visualizer/Web2.0 interface.
This is my pretty picture of what I mean and why it's important. It's not only about how quickly you can do a mashup, but how much time you have spent doing the traditional IT development and why this can only work in a light weight framework such as Mashups.
Mashup Model
skip to main |
skip to sidebar
Modern solutions and viewpoints on practical software development, not the text book stuff, or the stuff you put in proposals to impress people, but what really works. Other projects include: Divorce Support Site and All about Mashups
No comments:
Post a Comment