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.
