I assume client.total is automatically initialized to be equal to 0 for a
new CFID/CFTOKEN pair. If a new CFID/CFTOKEN was generated, then the old
CFID/CFTOKEN pair would still have the old value for client.total (namely
0) and so would the new CFID/CFTOKEN pair have the value 0 for client.total.
I had the same problem from time to time. Variables reverting to initial
values used to drive me nuts. For this and other reasons I went to a
cookie-less scheme where the CFID/CFTOKEN values are included in the URL,
thus automatically maintaining state from one page to the next. I then use
a different database from the one that stores CFID/CFTOKEN to store the
values of other "client variables"
Everything words fine. Except a new CFID/CFTOKEN is generated with each
page request. This is not a real problem, just an annoyance filling up the
database a bit with garbage (that I delete every 2 days). But I feel I
should be able to somehow stop generating new CFID/CFTOKEN pairs.
Keep us posted on what happens.
best, paul
At 10:45 AM 10/31/00 -0500, you wrote:
>somehow failing to pass the CFID/CFTOKEN pair with your request? If this
>were true, CF would not know which client vars to update, and your app would
>probably generate a new token pair for that request, and also behave as
>described.
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
