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.
Now, if there was something like... cgi.browser_instance, and it was unique
for each browser instance the user fired off, hoo baby, that would be
slick!!!!!
However, this is something that would have to be built into the -browser-,
and as such, its a major case of wishful thinking on my part...
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, March 01, 2001 7:50 AM
> To: Fusebox
> Subject: RE: Session VS. Client Vars
>
> If you do this shouldn't you might as well give up on cookies, and pass
> CFID/CFTOKEN in each URL?
>
> best, paul
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
