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

+1

----- Original Message -----
From: "John Fuller" <jfuller@wernervas.com>
To: "Christopher B Ferris" <chrisfer@us.ibm.com>
Cc: "Mark Baker" <distobj@acm.org>; <public-ws-addressing@w3.org>
Sent: Wednesday, November 24, 2004 4:32 PM
Subject: Re: Sample SOAP message on the wire with Reference Properties and
Parameters (without a wrapper!)


>
> 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:35:02 UTC