I do the exact same thing...

>From: "Gyrus" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: CF-Talk <[EMAIL PROTECTED]>
>Subject: Re: SUMMARY: Request Scope & Follow up Locking Questions
>Date: Tue, 13 Nov 2001 15:09:17 -0000
>
> > >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
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists


Reply via email to