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

[Anne Thomas Manes]

+1. 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.

Anne

On 7/14/06, Stefan Tilkov <[EMAIL PROTECTED] > wrote:

On Jul 14, 2006, at 9:52 AM, Harm Smit wrote:

> The latter is rubbish. It should read: lightbulb10.turnOn()
> Each lightbulb is an independent, autonomous service provider.

That's the first time I've seen someone make that claim for SOA-style
services.

Stefan
--
Stefan Tilkov, http://www.innoq.com/blog/st/

__._,_.___

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.

---

__,_._,___