In this case, you can't store that information in the session. You'd have to do something like passing all the request specific keys in the URL from page to page. ?confID=xxx. Then, when you build your URLs, pass them along on every link. There isn't a way to send different cookies back from different windows of the same brower...
On 10/30/12 4:58 PM, =?ISO-8859-1?Q?Claude_Schn=E9egans wrote: > >>You can prevent session-based race conditions by using CFLOCK around > any code that reads or writes session variables, > > It is not an issue of session race and I don't see how CFLOCK could help. > Imagine you have a big system designed to manage big events like annual > conferences wirh inscription, payments, etc.. > The first thing the user will do is select the conference he wants to work > with, then the id of this conference > is stored in a session variable. All he will do any further wil be done on > this conference. It is impossible to do anything without first selecting the > event. > But suppose he opens a new window in which he selects another conference, the > session variable will contain the id of this new event. > Then anything he does using the first window will be done on this new > conference, and this may cause trouble. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:353030 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
