Hmm my thinking is this...
If you put in an application scope the CF Server has to open up a new thread
for each application variable and you need to lock it. If you put it in the
request scope in the Application.cfm you don't have use CFLOCK. However if
you put it in the request scope you will be re-setting all the variables on
every single page call. Let's say you have like 50 application variables,
now you will be loading in these variables every single time. The
application variables were loaded only once per timeout. Which one is
really the advantage?
Won
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 11, 2001 2:02 AM
To: CF-Talk
Subject: Re: request scope revisted
All my DSNs are request-scope.
Advantage: No locking needed.
best, paul
At 05:44 PM 1/10/01 -0500, you wrote:
>Anyone out there set a request.dsn instead of an application.dsn?
>If so is there an advantage?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
