OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [sca-assembly] [ISSUE 33] Updated Proposal for Issue 33


Thanks for sending the updated version.

Three nits:

1) There is a lowercase 'must' in "... namely that the binding must be 
able to treat the transmission ...".
s/must/MUST/

2) For the same sentence, I prefer to talk about connections rather than 
treatment of transmissions. I would also like to change the requirement 
from 'must be able to' to 'it MUST'. I.e., it is not the capability that 
we are requiring, which may or may not be used at runtime, but that it 
must be so at runtime.
So the new suggested sentence would be:

"The requirements on a binding to support the asyncInvocation intent are 
the same as those required to support services with bidirectional 
interfaces - namely that the binding MUST [some-tag] send the response 
message in a separate connection from the one used by the request 
message, with an arbitrarily large time interval between the two 
transmissions.

3) In the "Implementation Type support", I would like to replace the 
"asynchronous client-side and asynchronous server-side mappings" with 
"non-blocking client-side and non-blocking server-side mappings/APIs". 
Talk of async/sync at the API-level when there is async/sync going on at 
the transport-level leads to too much confusion. Especially, when 
blocking APIs can be used with async transport and non-blocking APIs can 
be used with sync transport.

-Anish
--

Mike Edwards wrote:
> 
> Folks,
> 
> Here is an updated version of the proposal for Issue 33 following the 
> discussion on the call yesterday:
> 
> 
> 
> 
> This is the version that I am sending to the other TCs.
> 
> Note that the current Assembly specification does not define the 
> requirements that bidirectional interfaces place on bindings, so the 
> text in this proposal is the first place that this is defined for the 
> Assembly specification.
> 
> 
> 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/
> 
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]