Well, in my case, I gave up on CFID/CFTOKEN and "rolled my own" using my
own special client variable database. That way I guarantee my "CFID" is
unique across the server farm, and I store each client variable in its own
column (no more parsing of a #-delimited list).
It's not as convenient of Allaire's out-of-the-box solution, but it works
fine without a burp.
best, paul
PS> Of course, I pass my "CFID/CFTOKEN" in each URL.
At 08:04 AM 3/1/01 -0900, you wrote:
>Yeah, but... How do you get a unique cftoken? Remember, a browser spawn is
>an identical twin of its originator. The CF server has no way of detecting
>this and assigning a new cftoken. There aren't any CGI variables you can
>test for.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
