On Sat, 2005-12-31 at 07:29 +0000, Paul Fremantle wrote: > I know I'm late :) > > Here are my views: > > 1) Server sessions should be enabled by actual specific action of a > developer or deployer > > 2) Client sessions should be enabled by the following model: > a) If the programmer repeatedly uses the same instance of the same > stub then sessions will be *possible*. > b) Only if the server uses HTTP cookies or WS-A reference params > the session will be *actual*. > > i.e. for a session to take place, the consumer has to program in a > certain way AND the provider has to enable sessions.
Right. I think we're agreeing: - service's scope should be set by the user and the default can be application - client (stub instance) by default should, *IF* cookies show up on the wire, use them. If they don't nothing happens. In order to support that behavior, the stub should be default be configured to copy cookies from responses and send them back on requests. If the server doesn't send them nothing happens. Sanjiva.
