AIL PROTECTED]
cc:
Subject:Re: deploy problem.
would notwork.
Mr. Russell Butek,
Thank you for your prompt reply.
Although the behavior is bit different from I expected, but it worked fine.
A new client program, and its result are attached below.
Russell Butek wrote:
>
>
Russell Butek schrieb:
>
> OK, folks, what do y'all think? Since the session info ultimately resides
> in HTTPTransport, even though there are multiple services/stubs/Call
> objects, the cookie info is preserved. So if you turn on sessions, turn
> them off, and turn them back on again, you're s
ssion. Is this the proper behavior? Or should we get a new session each
time we call setMaintainSession?
Russell Butek
[EMAIL PROTECTED]
Akira Hirose <[EMAIL PROTECTED]> on 03/10/2002 07:49:13 PM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:Re
Mr. Russell Butek,
Thank you for your prompt reply.
Although the behavior is bit different from I expected, but it worked fine.
A new client program, and its result are attached below.
Russell Butek wrote:
>
> It isn't sufficient to tell the server that the service is session scope.
> The clie
It isn't sufficient to tell the server that the service is session scope.
The client must be aware of it as well.
locator.setMaintainSession(true);
Russell Butek
[EMAIL PROTECTED]
Akira Hirose <[EMAIL PROTECTED]> on 03/08/2002 12:39:50 AM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PRO
