sca-policy message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [sca-policy] [ISSUE 60] Clarify scope of ordered intent - PROPOSAL
- From: Simon Holdsworth <simon_holdsworth@uk.ibm.com>
- To: "OASIS Policy" <sca-policy@lists.oasis-open.org>
- Date: Thu, 16 Oct 2008 13:36:59 +0100
Mike,
Overall I'm happy with this proposed
resolution. My two comments:
"via a single service reference"...
should that be "via a single reference"?
"This
intent does not guarantee that messages that are sent by a service client
are delivered to the service implementation. "
- so while ordering in the sequence is guaranteed, there may be gaps in
the sequence. The impact of this is that a runtime must not deliver
out-of-sequence messages, and I suppose discard them id that happens -
rather than holding on to messages after a gap in the sequence and waiting
for the missing message to be delivered. Was that your intent?
Regards, Simon
Simon Holdsworth
STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair
MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK
Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898
Internet - Simon_Holdsworth@uk.ibm.com
Mike Edwards/UK/IBM@IBMGB
14/10/2008 10:11
|
To
| "OASIS Policy" <sca-policy@lists.oasis-open.org>
|
cc
|
|
Subject
| [sca-policy] [ISSUE 60] Clarify scope
of ordered intent - PROPOSAL |
|
Folks,
Following the discussion on yesterday's TC call, I make the following proposal
as the resolution of Issue 60, dealing with
the detailed wording required for the resolution:
This proposal relates to sca-policy-1[1].1-spec-wd-08.pdf:
Replace lines 1980 - 1988 with the following:
3) ordered – The binding implementation
guarantees that the messages sent by a service client via a single service
reference are delivered to the target service implementation in the order
in which they were sent by the service client. Note that this applies
whether or not the service interface is conversational and also is not
affected by the implementation strategy of the service implementation (eg
whether each successive service invocation is handled by a separate implementation
instance in the case of stateless services). This intent does not guarantee
that messages that are sent by a service client are delivered to the service
implementation. Note that this intent has nothing to say about the ordering
of messages sent via different service references by a single service client,
even if the same service implementation is targeted by each of the service
references.
For service interfaces that involve messages being sent back from the service
implementation to the service client (eg. a service with a callback interface),
for this intent, the binding implementation guarantees that the messages
sent by the service implementation over a given wire are delivered to the
service client in the order in which they were sent by the service implementation.
This intent does not guarantee that messages that are sent by the service
implementation are delivered to the service consumer.
Yours, Mike.
Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
Email: mike_edwards@uk.ibm.com
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]