>CFID and CFTOKEN are just references to information held in memory or in the
>client datasource. Giving a URL with the CFID and CFTOKEN to someone else
>will give them the information to retrieve that data in much the same way as
>a URL with say mysite.com/index.cfm?fuseaction=dspProduct&ProductID=23 will
>display the product number 23 from your database.
Ok. It's a good way to describe the functionality.
Now i understand it better.
Thanks.
>You don't _have_ to pass the CFID and CFTOKEN on the URL, because this
>information is stored in a cookie on the users computer. However, if the
>user does not have cookies enabled then the session will not be maintained,
>because CF will not be able to write to/read from the cookie containing the
>CFID and CFTOKEN for that session. This why it is recommended that you
>include the CFID and CFTOKEN on URLs.
If visitor accept cookies the problem is solved.
If visitor don't accept cookies, can i store cfid & cftoken in a session
variable to no have to pass the CFID and CFTOKEN on the URL?
What are the problems of session variables? Client vs Session variables?
>There are ways that you can determine whether a user has cookies enabled or
>not and then decide whether to append the CFID and CFToken to the URL.
Can you tell me where can i find some ways to determine that?
Thanks
Toni.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
