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 />
