Xing:
Since I was storing client variables in a database anyway, for this but
mainly other reasons I went to a scheme where I create CFI/CFT pairs
(analogous to CFID/CFTOKEN pairs) using my own algorithm. Since CFI is
incremented by 1 in a single table for each new user no matter how many
machines are in the server farm, it's not possible to have duplicate CFIs.
While I understand how machines in a farm could have the same CFID (because
CFAS in each machine generates CFID independently), I'm still surprised it
turned out to be such a problem.
best, paul
At 06:49 PM 12/19/00 -0800, you wrote:
>This is a pretty old post but given its importance as related to client
>variables I want to revist this.
>
>I have a system setup where two cf machines are tied together via dns
>round-robin and share the same database for client storage. As the number of
>simultaneous users increasesd, the number of users overstepping/intruding
>into other's client memory space have increased to such as a point that I
>had to store the IP of the client user as part of the client init and verify
>the user ip with the client var each time as not to assume the cfid/cftoken
>on the client browser do actually belong to them. I have not personally
>reproduced on my machines but given the hundreds of reports this is not a
>coincidence. Other than the round-robin setup there are nothing special
>about the way the client vars are stored in the database.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
