|
Hi Ron Sorry if my reply sounded flip! I didn't mean to sound as if I was dismissing the topic in a high-handed way. My sincere apologies. MVC applies at many levels, doesn't it - most enterprise systems, service-enabled or not, feature many instances of the pattern - which is where your Ruby on Rails example comes in. But your question was specifically about application of the MVC pattern to SOA. And it does seem to me that services are to components (or applications, or databases, etc) what views are to models. Gautham writes: The View is something which is volatile and hence can change over a Well, not really, Gautham. All software is volatile, isn't it, especially business software. The point of MVC is to decouple model changes from view changes. Just like SOA! I really think that what we talk about on this list is how to apply the MVC pattern to very large pieces of software. As many people would recognize (and I've personally said so in various of forms of print over the years), SOA is essentially the latest incarnation of a move towards software modularization that begin in the 1960s - a journey in which development of the MVC pattern at Xerox Parc was a landmark. -- All the best Keith http://keith.harrison-broninski.info Ron Schmelzer wrote:
__._,_.___
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
