Sure use javascript and submit it as hidden form variables to every page you
go to, but personally I'd think that was a bigger pain than just appending
to the url or setting a cookie.
Fred
----- Original Message -----
From: "Kevin Bridges" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 25, 2000 12:55 PM
Subject: RE: Maintaining Proper State
> I've "Read The F#@king Manual!" and then the Allaire Knowledge Base and
then
> The Cold Fusion Forums, and then Ben Forta's books, a really cool book
> Mastering ColdFusion by Arman Danesh and Kristen Motlagh, and followed
that
> up with a very good article in the Cold Fusion Developers Journal. Even
> thought I had a good understanding of it until I switched my client
storage
> to a database instead of cookies and saw the weird behavior I
"specifically"
> outlined below. That's when I decided to ask this list ... maybe I should
> re-phrase my question.
>
> Is it possible to accurately track state with cold fusion without planting
a
> cookie and without passing cfid and cftoken in the url. From the
different
> options I've seen it would seem that it is not possible.
>
> >From the plethora of posts and gripes I saw on Allaires site I'd venture
a
> guess that a very large number of users have issues with the way that Cold
> Fusion handles state ... and I was wondering what peoples best practices
> were.
>
> Sorry for not being explicit with the original question, but maybe this
will
> help clarify where I am coming from and why I ask.
>
> Thanks
>
> -----Original Message-----
> From: Nat Papovich [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 25, 2000 12:14 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Maintaining Proper State
>
>
> Don't take the silence of the list on this thread to mean we don't have
> anything to say. It's just such a HUGE topic that is pretty well covered
in
> all the ColdFusion books, and many of us are thinking "Read The F#@king
> Manual!"
>
> SoOoOo, if you have a more specific question about maintaining state, you
> might have better luck getting a response.
>
> Nat Papovich
> ICQ 32676414
> "Whatever you do may seem insignificant,
> but it is most important that you do it." -M. Gandhi
>
>
> -----Original Message-----
> From: Stewart, Mark [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 25, 2000 6:29 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Maintaining Proper State
>
>
> I'm interested in this thread as well. I've been reading up on this and
> haven't quite gotten it down yet. I've noticed the same thing myself, but
> not all the time. In some instances, the CFID & CFTOKEN stay the same when
> traversing my app, but in others, it changes. I know I'm missing a little
> tid-bit of information on this.
>
> I did read that you don't need to pass #urltoken# when you use
<cflocation>
> because it does it automatically for you.
>
> Anyway, I'm interested if someone can elaborate on state management.
>
> Thanks,
>
> ~Mark
>
> -----Original Message-----
> From: Kevin Bridges [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 24, 2000 2:09 PM
> To: FuseBoxList
> Subject: Maintaining Proper State
>
>
> Can anyone give a _good_ explanation of CFID/CFTOKEN & State Management?
> I've switched my client variable storage to a sql database in an effort to
> eliminate cookies and have been watching exactly what is being entered for
> the first time ... and it is confusing me.
>
> I can sit on the homepage of a server that is not getting hit by anyone
else
> but myself and watch three rows with 3 different cfid/cftoken get
generated.
> I place #URLTOKEN# at the very top (just under app_globals) and at the
very
> bottom of the page and both produce the same cfid/cftoken ... so, why are
> there three new entries in the database with different cfid/cftoken?
>
> Now, if I hit reload the cfid and cftoken that are being displayed on the
> page changes and three new entries are added to the database .... Since
I'm
> using the same application shouldn't I keep the same cfid/cftoken? If I
> store a series of client variables in the database and the end user hits
> reload ... a new session is created and all the client variables are no
> longer accessible unless I've somehow recorded what the cfid/cftoken was
> before they hit reload? Does this sound right?
>
> It would appear that you need to establish the application and then pass
> cfid/cftoken in every link, form, and cflocation to maintain state? Is
this
> correct?
>
> TIA
>
> --------------------------------------------------------------------------
--
> --
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
> --------------------------------------------------------------------------
--
> --
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
> --------------------------------------------------------------------------
--
> --
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
>
> --------------------------------------------------------------------------
----
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
>
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
