W3C home > Mailing lists > Public > public-sws-ig@w3.org > September 2004

Re: granularity/definition of a "service"

From: Pranam Kolari <kolari1@cs.umbc.edu>
Date: Thu, 16 Sep 2004 11:00:37 -0400
Message-ID: <4149AA95.40604@cs.umbc.edu>
To: Monika Solanki <monika@dmu.ac.uk>
CC: public-sws-ig@w3.org


>> Specifically, the other services that WSDL declares:
>> receive ( one-way operation)
>> receive, reply ( two-way )
>> pick, onMessage (one/two-way)
>> event, messageHandlers (one/two-way)
>> .....
>
>
> So communication primitives can indeed be classified as services as 
> per BPEL ?
>
>>
>> Note that "invoke" is not part of WSDL since it is used by the 
>> composition to invoke external web services and is not
>> a provided service by the composition. Ofcourse one could argue that 
>> certain "invokes: could be one-way operations
>> reporting to external entities.
>>
>> So in this sense, a subset of activities (combination of activities) 
>> are services as they serve clients. 
>
>
> I agree that a combination of activities can indeed represent a 
> service, but would an individual activity like for example <receive> 
> be classified as a service?

I would say a <receive> alone is a service if it represents a one-way 
operation  in the BPEL composition. <receive> can also be accompanied 
with a corresponding <reply> in which case both of them put together is 
a service. A subset of activities ( and a combination of activities) are 
services based on the way they serve clients.

-- Pranam
_____________________________________________________________________

Pranam Kolari 						
Department of Computer Science
University of Maryland, Baltimore County	 
Baltimore, MD 21250				

Contact:
(Work) +1 410 455 3971 :---: (Home) +1 410 536 4772
kolari1@cs.umbc.edu    :---: http://www.cs.umbc.edu/~kolari1
_____________________________________________________________________
Received on Thursday, 16 September 2004 15:00:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:32:46 UTC