W3C home > Mailing lists > Public > public-ws-addressing@w3.org > September 2005

Reference Parameters - using them

From: Pete Hendry <peter.hendry@capeclear.com>
Date: Thu, 29 Sep 2005 11:35:09 +1200
Message-ID: <433B28AD.5040008@capeclear.com>
To: public-ws-addressing@w3.org


Related to David's examples for i057, I was wondering about what I would 
consider the most common use-case for reference parameters - the server 
wanting the client to return context in the next request. It seems to me 
the current design of reference parameters are only useful for

a) fixed value data - i.e. not session-like data
b) the client asking the server to pass back information using the 
replyTo header

Consider the (common?) scenario where a client logs into a server. The 
server then creates a "session" in which it has customerKey and 
shoppingCartId values it wants the client to pass back in each 
subsequent request. These are opaque as the client does not have to know 
what the customerId or shoppingCartId are to work, it just has to 
include them as-is. ReferenceParameters seem the ideal vehicle for this 
but where would the server specify these parameters? They are not fixed 
values and will change for each "conversation" so they cannot just be 
specified in the WSDL with fixed values. They have to be parameterized 
somehow to allow the server to set the actual session values and pass 
them to the client to be included in the next request.

Is this beyond the scope of reference parameters? In (my understanding 
of) their current form they are of little use. It is unlikely you would 
want to publish fixed values within parameters in WSDL (or any other 
static mechanism) and less likely that the client would start the 
session information that could be contained within them.

Pete
Received on Wednesday, 28 September 2005 23:35:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:09 GMT