W3C home > Mailing lists > Public > public-ws-addressing@w3.org > November 2004

Re: Sample SOAP message on the wire with Reference Properties and Parameters (without a wrapper!)

From: John Fuller <jfuller@wernervas.com>
Date: Wed, 24 Nov 2004 10:32:22 -0600
Message-Id: <6ABD175C-3E36-11D9-8F2A-000393B3C0BA@wernervas.com>
Cc: Mark Baker <distobj@acm.org>, public-ws-addressing@w3.org
To: Christopher B Ferris <chrisfer@us.ibm.com>

As stateful sessions go, wouldn't something like WS-Context be more 
appropriate?

On Nov 24, 2004, at 10:01 AM, Christopher B Ferris wrote:

>
> The ref props/params *can* be used to provide additional information 
> that
> the service provider will use
> as it sees fit. One such purpose that has been used by WS-RF has been 
> to
> pass keys/identifiers to
> resources (implied resource pattern) as ref props, but that is not the
> only use of ref props/params.
> In the context of the implied resource pattern, the ref props 
> serialized
> as SOAP headers can be
> considered the equivalent of cookies used to associate a stateful 
> session,
> like a shopping cart service
> might do.
>
> As an example that is often used, a service might have three levels of
> service; silver, gold and platinum.
> Each level of service might have a different policy that applies. 
> Hence, I
> would use the ref props to
> include a <myservice:MembershipLevel> element with the possible values
> Silver, Gold, or Platinum.
> Is that identity? Nope.
>
Received on Wednesday, 24 November 2004 16:33:16 GMT

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