|
Patrick wrote:
>> Whether this approach is suitable or appropriate in the
business
>> processes context I do not know. > Yes, that is more my question. I would not expect this to be part of a > business-level "choreography" On reflection I think that, fun though it is, the
kind of buffering solution I suggested would be unwise in the context of
business processes. For instance, if you have messages whose semantics are
dependent on their context in the exchange, you could have nasty
results.
I think that the formulation of a choreography for
the collaboration should ensure that the abstract processes of the participants
are compatible. If the sequence of message exchanges then violate the
choreography, this should be handled manually as an exception
situation.
Rgds
Ashley
__._,_.___
SPONSORED LINKS
YAHOO! GROUPS LINKS
__,_._,___ |
- Re: [service-orientated-architecture] Re: Orchestratio... Steve Ross-Talbot
- [service-orientated-architecture] Re: Orchestrati... patrickdlogan
- Re: [service-orientated-architecture] Re: Orc... Ashley at Metamaxim
- [service-orientated-architecture] Re: Orc... patrickdlogan
- Re: [service-orientated-architecture]... Ashley at Metamaxim
- Re: [service-orientated-architec... Steve Ross-Talbot
- AW: [service-orientated-architec... Frank Leymann
- Re: [service-orientated-architecture] Re: Orchest... Ashley at Metamaxim
- AW: [service-orientated-architecture] Re: Orc... Frank Leymann
- Re: [service-orientated-architecture] Re:... Ashley at Metamaxim
- Re: [service-orientated-architecture]... Steve Ross-Talbot
- Re: [service-orientated-architecture] Re: Orchest... ash galal
- Re: [service-orientated-architecture] Re: Orc... Alexis Richardson
