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 -
use something like
cfset request.var=Duplicate(session.var
Terry Hogan wrote:
My last question was:
4. What about locking? I've read that Request Variables
don't need to be locked. Is that true? Why not?
Dave Watts Replied
They don't need to be locked, because they're not persistent memory
variables.
I would rephrase that as:
They don't
Hi Terry,
It's a very nice summary, however, I have some thoughts after reading.
A couple of notes here: if you do this, use something like
cfset request.var=Duplicate(session.var)
to transfer the variable. If you don't use Duplicate() - correct
me if I'm wrong someone! - then request.var
Scope Follow up Locking Questions
Hi Terry,
It's a very nice summary, however, I have some thoughts after reading.
A couple of notes here: if you do this, use something like
cfset request.var=Duplicate(session.var)
to transfer the variable. If you don't use Duplicate() - correct
me if I'm
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
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
situations.
-Original Message-
From: Mike Townend [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 13, 2001 10:16 AM
To: CF-Talk
Subject: RE: SUMMARY: Request Scope Follow up Locking Questions
But surely that means that CF is using double the memory for every
request... Memory
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..
Tis true, but the sites I've done so far aren't generally high-traffic
sites, and there haven't been any problems. In fact, 99% of the
Plus, my guess is/was that the general server load would be
balanced out by the reduction of any number of CFLOCKs down
to one (in application.cfm) - tho this could be a wrong-headed
way of thinking about it.
Anyone got any opinions - even better, stats! - on the impact of
using this
.
- Original Message -
From: Dave Watts [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Tuesday, November 13, 2001 12:09 PM
Subject: RE: SUMMARY: Request Scope Follow up Locking Questions
Plus, my guess is/was that the general server load would be
balanced out by the reduction of any
10 matches
Mail list logo
