But surely that means that CF is using double the memory for every request... Memory to store the session details and memory to store the session details..
Whats wrong with setting CFAdmin to automatically lock reads... That way any time you read a shared var ie IsDefined and DSN's etc its already locked... Then all you have to do is lock the writes.. -----Original Message----- From: Gyrus [mailto:[EMAIL PROTECTED]] Sent: 13 November 2001 15:09 To: CF-Talk Subject: Re: SUMMARY: Request Scope & Follow up Locking Questions > >use something like > ><cfset request.var=Duplicate(session.var)> > >to transfer the variable. > > I think to use request.var this way you can only read the variable. Absolutely - maybe I should have said. I generally transfer session variables into the request scope in application.cfm so that I don't have to worry about locking every time I want to read a session variable (90% of my use of session variables). Of course, if I need to update a session variable, I use a lock for writing to the session variable itself, and the updated value gets read back into the request scope next time round (you can update the corresponding request variable immediately if the value might be needed within the same request, naturally). - Gyrus ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
