Regardless of where it is done, it is not in scope for the RM since that
is an implementation detail (the "where").
There is a possible item for consideration if we were to buy into the
stateless argument, WRT the processing model for a service. That is
weak at best.
Duane
wrote:
>Martin,
>
>I believe we went through that one.
>
>Services are autonomous maintaining their own state.
>
>Service combining and subsequent state management is maintained by a higher order concept (orchestration) which is not in the RM
>
>At least I think this is the consensus??
>
>Wes
> -----Original Message-----
>From: Smith, Martin [mailto:]
>Sent: June 13, 2005 3:14 PM
>To: Duane Nickull; Breininger, Kathryn R
>Cc: SOA RM
>Subject: RE: [soa-rm] Wikipedia definitions FYI
>
>So, where exactly is state maintained in an SOA??? Going to be tough to
>execute transactions without state.
>
>Martin
>
>
>-----Original Message-----
>From: Duane Nickull [mailto:]
>Sent: Monday, June 13, 2005 3:02 PM
>To: Breininger, Kathryn R
>Cc: SOA RM
>Subject: Re: [soa-rm] Wikipedia definitions FYI
>
>The comment about services being stateless is interesting. If we agree
>with that assertion, it may affect the notion of a service processing
>model (request to many responses). Also - that seems to be more tied to
>
>the nature of the transport/binding mechanism itself.
>
>Duane
>
>Breininger, Kathryn R wrote:
>
>
>
>>Just an FYI. I see Wikipedia is beginning to work on definitions for
>>SOA as well:
>>
>>http://en.wikipedia.org/wiki/Service-oriented_architecture
>>
>>Kathryn Breininger
>>CENTRAL Project Manager
>>Emerging Technologies
>>Boeing Library Services
>>
>>425-965-0182 phone
>>425-237-3491 fax
>>
>>
>>
>>
>>
>>
>>>How was your service? Please click link below.......
>>>http://socal.web.boeing.com/ssglibsurvey/
>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
>
