Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
Date: Sun, 27 May 2001 15:06:06 -0700
From: Rob Jellinghaus <robj@unrealities.com>
Subject: Re: Session support
In-reply-to: <01a801c0e6ee$0f027c80$0b00a8c0@gamebox>
To: axis-dev@xml.apache.org, axis-dev@xml.apache.org
Message-id: <3.0.1.32.20010527150606.0109ae28@shell2.ba.best.com>
MIME-version: 1.0
Content-type: text/plain; charset="us-ascii"
References: <3.0.1.32.20010527133327.0109ae28@shell2.ba.best.com>

At 04:46 PM 5/27/2001 -0400, Glen Daniels wrote:
>> >With a system like this in place, you could also write a simple
>SOAP-based
>> >session management system which uses SOAP headers to carry session-ids,
>> >which tie to Hashtables that are pooled and expire.  Any
>> >Handler/extension/backend who wants to store stuff in the session bag
>> >doesn't need to care how the actual session is being managed.  The
>> >RPCDispatch sample code above wouldn't change a bit.
>>
>> This will be just as true in the code I next submit.
>
>Hm.  OK, that seems a bit at odds with your last paragraph.

I see your point.  Well, I'll go with putting the object table in the Java
provider (simply to bring the Java provider up to Apache SOAP-like
functionality).  One small step at a time....

>I'm psyched to see it!  Did you get your CVS access working yet? 

No, no mail from root yet :-( :-( :-(

>When do
>you think this might be ready - it's got the ServiceClient stuff in it too,
>right?

Right.  I should have it ready on Tuesday.  That work?
Cheers,
Rob