Another solution is to "roll your own"
Don't use CFAPPLICATION
Manage your Client variables in your own app-specific database.
Works fine here. Another instance is another client.
I'd show you but NorthPoint toasted me.
best, paul
PS> I guess we 'net denizens have a new verb, like: "I've been NorthPointed"
At 08:21 AM 4/3/01 -0800, you wrote:
>I'll toss in a caveat that I have yet to lick...
>
>With the client variable/WDDX scheme, although it works gangbusters, you
>will run into big problems if and when a user spawns a new browser instance.
>The server has no way of knowing this new spawn is to be given a separate
>client store. When the user goes in two different directions with the two
>instances (and who amongst us hasn't done that?), you end up with a mess on
>the server side. Is Joe Shmoe adding an item to the cart or is he removing
>one? Did he log out?
>
>The only solution I know works in a controlled intranet environment. Tell
>the users not to spawn multiple instances. That, however, is hardly a
>solution.
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
