I'm not a CF-internals expert, but is it possible the CFID and CFTOKEN are
being kept in some way and therefore the session variables are persisting in
this case? Either the cookies are not expiring themselves, or perhaps they
are being passed in the URL from a cached request in the history of the
browser?
Just a thought (or two..)
-Bill
/intraget
----- Original Message -----
From: Bill Killillay <[EMAIL PROTECTED]>
To: CF-Talk <[EMAIL PROTECTED]>
Sent: Saturday, November 25, 2000 4:26 PM
Subject: RE: Structures: Where is data kept
> You know they don't and I know they don't, but earlier in
> this thread the gentleman said they where making it across
> "reboots". The only thing that would explain that is if the
> data was being held in a cookie. Now I guess the question
> is which machine is he talking about the reboot on. If it's
> the Client machine, then it makes perfect sense as the
> cookies are like David Watts pointed out the CFID and
> CFTOKEN which act as pointers to the session stored in the
> memory on the server. However if he was talking about the
> server being rebooted then there is something else that is
> not being brought into this thread. That is all I was
> meaning.
>
> Bill
>
> > -----Original Message-----
> >
> > They don't.
> >
> > >Then how would the persist across the reboots?
> > >
> > > > -----Original Message-----
> > > > > Session variables are stored in client side
> > > > cookies and/or
> > > > > server memory. They DO NOT get stored in the
> > > > registry. The
> > > > > variables that get stored in the registry are Client
> > > > > variables. There is a BIG difference in
> > the two. For
> > > > > example you cant story a structure in a Client
> > > > variable with
> > > > > out using WDDX on it, etc. Hope this helps
> > a little.
> > > >
> > > > Session variables are NOT stored in client-side
> > > > cookies. They're always
> > > > stored in memory. What is stored in cookies are
> > > > the two tokens CF uses to
> > > > associate a user's browser with those variables
> > > > stored in memory.
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
>
> Archives: http://www.mail-archive.com/[email protected]/
> Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
