Kola, > > One solution is to create an application scope structure > which contains > each sessions session.sellcustomer id. You should then be > able to refer > to a particular session. You may also want to store the time > of the last > request so you can expire users after a period of inactivity. > > If you are using CFMX there may be more elegant solutions available. >
Thanks, this is pretty much what I had in mind, but how do I actually retrieve the session.sellcustomer variable from each active session to place them into my structure? I am using CFMX. If I can't access variables from other users' sessions (which I doubt I can) then its looking like I may need to use a database solution instead. However this would adversely affect the real-time element I want. Dave ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
