--- In [email protected], Keith Harrison-Broninski <[EMAIL PROTECTED]> wrote: > > Robin wrote: > > >Keith, > >I can share my experience on services reuse in a Telco environment. > >We had something 600 different services in production. Each service > >had one and only one operation. > > > > > That's interesting. Can you say anything about the nature of the > operations? > > Having only one operation per service suggests that they were > document-oriented - e.g, "here's a purchase order, do something to it > and give the updated version back (or pass it on)". Such a REST-like
Agree it's a little REST like but I'm not sure I'd map that cleanly from a REST-like set of services (that is a set of URL structures) to a single method per interface. Potentially, for a single URL of a REST implementation I've got the CRUD operations. I might only have a read operation of course or a create operation but all of those operations could be performed by a single service couldn't they? A couple of references that I was considering as I replied to your posting: http://www.xfront.com/REST-Web-Services.html http://www.xml.com/pub/a/2005/03/02/restful.html What do you think? Best wishes, Dan. 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/
