-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
> When the client gets in contact with Jserv 2, he has an old session-id
> cookie with him but no session object in Jserv 2, so Jserv 2 creates a new
> session for him (not what I wanted). If any JServ developers read this, I
> would be most pleased if someone creates a possibility of a session-data
> 'share', from where Jserv 2 could fetch the old session-data linked to
> that 'dead' session-id! This would require some sort of 'distributed
> shared memory' -solution, database or some other other container. Load
> balancing would be much more fault tolerant after that.
I believe that you are going to either have to wait till a later release or
the quickest and easiest solution would be to handle sessions yourself in
your own code.
-jon
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
