On Jul 2, 2006, at 10:58 AM, Harm Smit wrote: > IOW, using your terminology, in my example the center of the design > is the capability of an individual lightbulb. This capability is > exposed through three operations: turning it on, turning it off, > dimming it. > I don't see how this misses the mark on SOA.
In a SOA you would never *expose* these operations as an object +methods. You'd create a service that implements some business functionality (e.g. a building's light control service). This service then would act as a facade to the actual light bulbs (and what not). Doing the same with REST does mean providing resource abstractions for the light bulbs, BUT ONLY through the HTTP interface (again as a facade). It does not mean exposing any legacy light bulbs or light bulb controlers. So, if you directly expose the three operations, you miss the SOA point - either way. Jan ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
