W3C home > Mailing lists > Public > www-ws-arch@w3.org > May 2003

RE: WSA architectural concepts and relationsihips related to WS, SOA , and the Web

From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
Date: Tue, 6 May 2003 17:47:17 -0400
Message-ID: <9A4FC925410C024792B85198DF1E97E40598586D@usmsg03.sagus.com>
To: www-ws-arch@w3.org



> -----Original Message-----
> From: Cutler, Roger (RogerCutler) 
> [mailto:RogerCutler@ChevronTexaco.com]
> Sent: Tuesday, May 06, 2003 4:07 PM
> To: Champion, Mike; www-ws-arch@w3.org
> Subject: RE: WSA architectural concepts and relationsihips related to
> WS, SOA , and the Web
> 

> The "service" entry raises a lot of questions in my mind, 
> however.  Why
> did you find it necessary to use the term "course-grained" when you
> defined service?  "Course-grained" on what scale? 

In retrospect, that's probably more best practice for a useful service than
a definition of SERVICE.  A service (any sort) has got to do enough work to
justify the overhead of the remote invocation.  I'm happy to remove that.

> Well defined
> "operation" or "interface"?  Is there a meaningful 
> distinction there and
> if so why did you use "operation"? 

It is hard to define "service" without using the term "serve" or "service."
The best I can do is to say that a service *does* something; "performs an
operation"  sees like a better phrase than "does something" :-)  

An interface specifies how one requests the service to perform that
operation / do something.  Is that a reasonable distinction?  
Received on Tuesday, 6 May 2003 17:47:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:18 GMT