Re: [service-orientated-architecture] Zapthink on SOA/REST

[Ashley at Metamaxim]

Anne wrote   > In a traditional service-oriented approach, a service implements a function that can be performed > on multiple instances of a resource. You do not have a different service for each resource. > .e.g, you have a stockQuote service -- you input a stock symbol and it returns > the stock quote for that stock symbol. You don't define a separate service for each stock symbol. > The latter would be a resource oriented approach -- and it makes much more sense to use a uniform > interface( i.e., REST) when using a resource-oriented approach. The more I hear about the REST paradigm, the more I think it is very similar to that proposed by the advocates of "Naked Objects" ( http://www.nakedobjects.org/ ). Although Naked Objects is concerned with the interface presented to humans (rather than a service interface presented to other systems) their object-based interface seems very similar to the REST resource-based interface.   Is anybody else on this list familiar with Naked Objects and, if so, do you agree with the similarity I suggest?   Rgds Ashley __._,_.___ SPONSORED LINKS Computer software Computer aided design software Computer job Soa Service-oriented architecture YAHOO! GROUPS LINKS  Visit your group "service-orientated-architecture" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___