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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

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


Subject: RE: [ws-rx] Issue 28: MakeConnection preconditions are unclear



As a sender of messages I certainly would like to know if I will be able to get my responses - and likewise, as a server I'd like to know if the client has an intention of polling.  If they're not going to poll then I would think the server could (would) make some very different choices.  For example, it may reject the incoming message (CS or app) or it may choose to not turn on RM (when optional) for responses.  I think a policy assertion (or something like that) on the server side is needed for the client to make smart choices, and (not surprisingly) the use of the RManonURI is the client's way of indicating to the server of its intention to use MC.  I see no similar signaling mechanism in either of the other MC proposals.

thanks
-Doug

__________________________________________________
STSM | Web Services Architect | IBM Software Group
(919) 254-6905 | IBM T/L 444-6906 | dug@us.ibm.com



Marc Goodner <mgoodner@microsoft.com>

11/14/2006 11:59 AM

To
Doug Davis/Raleigh/IBM@IBMUS
cc
Jonathan Marsh <jonathan@wso2.com>, "ws-rx@lists.oasis-open.org" <ws-rx@lists.oasis-open.org>
Subject
RE: [ws-rx] Issue 28: MakeConnection preconditions are unclear





I think that needing to know before/after the CS is sent is a matter of opinion. I certainly don’t see anything in the current spec that explains what the precondition requirements are around setup for future MC before CS.
 
I’m not exploring an assertion for MakeConnection. I’d started looking at that for issue 15 but haven’t reached any conclusions yet.
 
From: Doug Davis [mailto:dug@us.ibm.com]
Sent:
Tuesday, November 14, 2006 8:55 AM
To:
Marc Goodner
Cc:
Jonathan Marsh; Marc Goodner; ws-rx@lists.oasis-open.org
Subject:
RE: [ws-rx] Issue 28: MakeConnection preconditions are unclear

 

Sorry, not true.  MSFT's proposal does not address any preconditions since the ability to support MC should be known before the CS is sent, not after.  Sending a MCRefued in response to a MC is too late in the game.  No matter which version of MC lives on I think some policy assertion will be needed so the server-side can advertise that it will support MC, or not.  I was assuming we could use this issue to add that.


As for Jonathan's text about either side needing to be in possession of the RManonURI - short answer is 'no' - only the minter (client) needs to know what the value is.


thanks
-Doug

__________________________________________________
STSM | Web Services Architect | IBM Software Group
(919) 254-6905 | IBM T/L 444-6906 | dug@us.ibm.com


Marc Goodner <mgoodner@microsoft.com>

11/14/2006 11:34 AM


To
Marc Goodner <mgoodner@microsoft.com>, Jonathan Marsh <jonathan@wso2.com>, "ws-rx@lists.oasis-open.org" <ws-rx@lists.oasis-open.org>
cc
Subject
RE: [ws-rx] Issue 28: MakeConnection preconditions are unclear

 







In the proposal we made for PR001 I don’t believe the below is an issue. The expected setup for MakeConection is defined.

 
I agree that if we close PR001 with no action that the current spec will need to be changed to address this problem.

 
 
From:
Jonathan Marsh [mailto:jonathan@wso2.com]
Sent:
Monday, November 06, 2006 9:46 AM
To:
ws-rx@lists.oasis-open.org
Subject:
[ws-rx] New issue: MakeConnection preconditions are unclear

 

MakeConnection as defined today relies on the RM Anonymous URI template.  The spec does not adequately specify the preconditions necessary for the exchange to be successful.

 
Prior to a MakeConnection message, do both the client and the server have to be in possession of a correctly constructed instance of the RM anon URI template?  Of an EPR using this template?  The example messages invent a subscription operation in step 1, which indicates that the precise URI and the intent to enable MakeConnection must be negotiated between the RMD and RMS out of band, yet nowhere are these preconditions enumerated.  The RM protocol preconditions only list an EPR as a precondition, not the precise form of that EPR, and any intention that buffering of messages should be engaged.  What happens if a client does a MakeConnection without all preconditions being satisfied also appears to be underspecified.

 
Jonathan Marsh
- http://www.wso2.com - http://auburnmarshes.spaces.live.com
 



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