Jonas Wallenius wrote:
> (a long posting about how to deal with stateful objects when failover and load
balancing are an issue)
One way to do this is to store the state on a database. The trick is to use a
key that is specific to the particular client session, rather than specific to
the object(s) that client is working with. Since every system can access the
database there are no "affinities", so failover and loadbalancing are easy. The
main issue with this is how does the session state data get cleaned out of the
database if the client simply goes away, and the usual answer is to periodically
delete old data.
Of course persisting session state will reduce peformance, but the designpoint
scales beautifully so you can simply throw a bit more hardware at the problem.
Ian McCallion
CICS Business Unit
IBM Hursley
[EMAIL PROTECTED]
Tel: ++44-1962-818065
Fax: ++44-1962-818069
===========================================================================
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".
