Next in thread → Next in month →

Re: FW: [ws-rx-implement] Phase1 Interop Endpoint for SAP (updated)

From
Eoug Eavis
Date
2006-10-25T10:02:46+00:00
ID
Thread
Re: FW: [ws-rx-implement] Phase1 Interop Endpoint for SAP (updated)
Actually, I think the text there is
ok because its talking about the Offered sequence, in which case the RMS
and RMD have been switched.  In other words, the reference to RMS
is to the RMS of the Offered sequence not the original Sequence.

-Doug











"Videlov, Vladimir"
<> 

10/25/2006 05:07 AM






To

<>




cc






Subject

FW: [ws-rx-implement] Phase1 Interop
Endpoint for SAP (updated)














 

Just forgot to mention that the
MUST NOT part of /wsrm:CreateSequenceResponse/wsrm:Accept/wsrm:AcksTo
is incorrect (wsrm-1.1-spec-cd-04).
It concerns Acks from RMS to RMD not the other way. Sorry for the spam
if this is a known issue.


Vladimir




From: Videlov, Vladimir [mailto:]


Sent: 25 ïËÔÏÍ×ÒÉ 2006 Ç. 11:51

To: Doug Davis

Cc: 

Subject: RE: [ws-rx-implement] Phase1 Interop Endpoint for SAP (updated)



Hi Doug,

 

You are right and I have fixed
this. Do you think that its worth to be mentioned in the spec that in this
case AcksTo URI can't be anon. Its mentioned that it can't be none, but
in the current scenario (3.1) it may lead to misunderstandings? At least
my understanding is that flagging the AcksTo to anon may be considered
as sending the Acks within the HTTP requests (the one and only available
channel). What do you think ?

 

Vladimir




From: Doug Davis [mailto:]


Sent: 25 ïËÔÏÍ×ÒÉ 2006 Ç. 00:52

To: Videlov, Vladimir

Subject: RE: [ws-rx-implement] Phase1 Interop Endpoint for SAP (updated)




ok - your AcksTo on the CreateSequenceResponse can not be anonymous - it
has to be a real URI since your messages are flowing over HTTP response
flows. 

-Doug 





 <vv:snip />
Next in thread → Next in month →