RE: [ws-rx-implement] Groups - InteropScenarios.doc uploaded

["Videlov, Vladimir" <vladimir.videlov@sap.com>]

Hi Dan,

Sorry for the late joining in on this issue ("last message" notification
to RMD), but why you decided to use an flag within the business
operation payload instead of CloseSequence for example? This flag will
never go to the RM layer at least in our impl.

I'm not following the WS-RX TC closely, so that the answer could be
obvious, but this solution bothers me a lot.

 
Kind regards, 
Vladimir Videlov 

-----Original Message-----
From: millwood@uk.ibm.com [mailto:millwood@uk.ibm.com] 
Sent: Friday, February 10, 2006 1:31 PM
To: ws-rx-implement@lists.oasis-open.org
Subject: [ws-rx-implement] Groups - InteropScenarios.doc uploaded

As requested on the call yesterday, I have updated the interop doc with
the
following changes:


For scenarios 2.1, 2.2 and 2.3, indicate in the last application request
message that it is the last one and how many were sent, so that the RMD
knows when it can close the sequence for replies.

I have added a missing Clients TerminateSequence Message example for
scenario 2.1
I have added a note about how the offered sequence should be used
pending
resolution to issue i090 for scenario 2.1

Please review and let me know of any problems.

Thanks, Dan


 -- Mr. Daniel Millwood

The document revision named InteropScenarios.doc has been submitted by
Mr.
Daniel Millwood to the WS-RX Implementation SC document repository.
This
document is revision #2 of InteropScenarios.doc.

Document Description:
Initial interop scenario doc

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/ws-rx-implement/document.ph
p?document_id=16617

Download Document:  
http://www.oasis-open.org/apps/org/workgroup/ws-rx-implement/download.ph
p/16617/InteropScenarios.doc

Revision:
This document is revision #2 of InteropScenarios.doc.  The document
details
page referenced above will show the complete revision history.


PLEASE NOTE:  If the above links do not work for you, your email
application
may be breaking the link into two pieces.  You may be able to copy and
paste
the entire link address into the address field of your web browser.

-OASIS Open Administration