I thought the only time you had a problem with a client var and cflocation is when you 
set you first visit a given site *and* set client vars *and* use a cflocation.  At 
that point cfid/cftoken is getting set on the same page as a cflocation gets run.  
Thus you lose that key pair, and along with it any cvars dependent on it.  But once 
the key pair is etched in digital stone you should be pretty much safe.

There's a KB article on this somewhere.

---------------------------------------
Matt Robertson    [EMAIL PROTECTED]
MSB Designs, Inc., www.mysecretbase.com
---------------------------------------


---------- Original Message ----------------------------------
from: Todd <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
date: Fri, 12 Jul 2002 18:57:36 -0400

I hadn't really started messing around with client variables until just 
recently.  So... I have this WDDX packet inside a client variable and 
storage is in a database rather than cookie or registry based.  I know I've 
read a lot of things that basically said, becareful with cflocation and 
client variables, but honestly -- I have an app that uses client variables 
and I have a the value of a createUUID() inside a wddx packet ... and, it's 
not changing - even after doing a cflocation, I'm not losing my client 
variables.

Am I lulling myself into a false sense of security here or ... is this 
fixed in cfmx? or ..?

Thanks,
~Todd


Todd Rafferty ([EMAIL PROTECTED])
http://www.web-rat.com/
Team Macromedia Volunteer for ColdFusion
http://www.macromedia.com/support/forums/team_macromedia/
Moderator @ FlashCFM.com - http://www.flashCFM.com/
Back-end Moderator @ Ultrashock.com - http://www.ultrashock.com/


______________________________________________________________________
This list and all House of Fusion resources hosted by CFHosting.com. The place for 
dependable ColdFusion Hosting.
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to