Alan,
This is not a db issue, and not even a client variable issue - it's just an
issue of workflow and application design (the same could happen with session
variables).
The problem really is you are getting calls for a page which then uses
persistent data (session or client) from a previous request. My fix for this
is as follows:
1. avoid as much as possible persistent data and pass the data back and
forth to the client on the url or as hidden wddx form fields - this solves
the problem but is not always possible to implement.
2. when I rely on persistent data I use a flag on the url UseSession to tell
the app if to use the stored variables or not.
>Problem is, with the db-driven client vars I'm using, I'm seeing a lotta
>errors due to the same client vars being used even though those separate
>instances of IE are doing different things...
Solution 2 is not fool proof - e.g. if a search app stores the criteria in
session vars and then has links for next results, then if the same user
performs two different searches in two different windows, hitting next in
the first window will then go to the next results of the *second* search -
*by design* !
HTH,
Noam
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
