We use sticky in the cluster while maintaining a session ID in client
scope. (sticky is better for us because we're dealing with reporting) If
server fails over, user is re-authenticated based on the session id,
then request is processed, transparent to the user. (Our authentication
takes place outside the cluster itself - single sign-on)
Best of both worlds, works great!
Stace
_____
From: Mike Brunt [mailto:[EMAIL PROTECTED]
Sent: October 3, 2003 5:05 PM
To: CF-Talk
Subject: RE: Session Variables Or Client Variables (Pros & Cons - Poll)
Joe, we have used Session variables more than Client. We typically use
duplicate to copy in and out of request so all but those var reads and
writes can be done in request scope avoiding extensive locking.
Obviously load-balancing can be an issue but setting sticky can mitigate
that. So the only real downside is in a fail-over situation.
In the J2EE version of CFMX you can utilize the underlying Java Session
replication mechanism.
Kind Regards - Mike Brunt
Original Message -----------------------
Personally i am not a big fan of Client Variables due to DB
Serialize/De-Serialize Overhead
and not being able to store complex variables etc...
Just Curious..
What would be the CF Developer Consensus to using Client Variables Or
using Session Variables?
Thanks,
Joe Eugene
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
