datasource. Another possible option?
Stace
_____
From: Joe Eugene [mailto:[EMAIL PROTECTED]
Sent: October 3, 2003 4:59 PM
To: CF-Talk
Subject: Re: Session Variables Or Client Variables (Pros & Cons - Poll)
Yes, you can manipulate your session variables all in one place and copy
them to variable/request scope for viewing purposes.
I agree, the down-side is fail over in versions where you cannot do
session replication.
So its kinda hard to choose cause it seems session/client vars both
seems to have equal points..
but which one would be better?
Joe
----- Original Message -----
From: Mike Brunt
To: CF-Talk
Sent: Friday, October 03, 2003 5:05 PM
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]
