>
> Ummm, I don't really know what HttpSession data is, but it sounds
> supiciously like something in a servlet engine. How does this work
> in a clustered environment in which a user might find themselves on
> any of the cluster members, and need to have access to their session?
> I think that's why StatefulSessionBeans (preferably persisted to a
> database) are useful... does that sound right?
>
Use Persistent sessions. Some of the Appservers support it. As far as my
experience with WebSphere goes, the session will be persisted between calls
to the admin database (DB2 or Oracle) or to an stateful EJB. It is just an
admin switch, no programming involved. The nice thing about this, is that
you are still using the SUN speced API to store sessions, but now, they work
transparently in a clustered environment, even if you implement a non-sticky
affinity clause in your network dispatcher.
I read that Gemstone also does this. I am sure someone from Gemstone will
provide the necessary details. I don't have enough experience with the other
app servers to know if they support persistent sessions.
The appservers will take care of the programming and optimising the access
to the session object in a fast, reliable way, which is the entire point of
using the J2EE architecture : leave all this infrastructure stuff to the
application server.
-- Aravind
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
