(B----- Original Message -----
(BFrom: "David Peterson" <[EMAIL PROTECTED]>
(BTo: <[EMAIL PROTECTED]>
(BSent: Wednesday, January 15, 2003 12:02
(BSubject: Re: Stateful Web Services
(B
(B
(B>
(B>
(B> Thanks Barry,
(B>
(B> This was the kind of "statefulness" and "persistence" that I am
(B> interested in (though I was also interested to hear what was said re
(B> SOAP and sessions by Anne et al., as this was another question I had).
(B>
(B> Can you tell me, why does the client need to set "maintain sessions" to
(B> TRUE (Axis) (or use the cookie container in .NET). I would have thought
(B> that for the example (bank account) that you and I describe,
(B> preservation of state would be an entirely server-side consideration,
(B> with no client-side requirements other than a valid SOAP invocation?
(B
(Bthe client needs to provide some means of identifying the call, so as to
(Bbind it to a session, otherwise the server doesnt know which session to
(Bassociate with a call.
(B
(BAll the session data can live server side, or you can send it back
(Bserialized and encrypted inside soap headers, if you so desire.
