That is correct. I use part of the fusebox methodology for this. In my
root directory of the web server I have a file that I keep all constants,
such as application name, the beginning of the page title (e.g.
"ThisSite.com -") and then just add the to that variable depending on what
part of the site you are in, and the datasource. You just include this
contant file every time and the request scope doesn't need locking. Just
another way you can do things that I like quite a bit.
----- Original Message -----
From: "Todd Ashworth" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Monday, December 11, 2000 2:37 PM
Subject: Re: Application.variables vs local.variables
> Yes, but then would you not have to lock it every time you ran a query?
At
> the least, you would need to lock the variable and set it = to a temp
> variable on every page you are going to use it. I would think this would
> negate any performance gains, or am I just off?
>
> Todd Ashworth
>
> ----- Original Message -----
> From: "Simon Horwith" <[EMAIL PROTECTED]>
> To: "CF-Talk" <[EMAIL PROTECTED]>
> Sent: Monday, December 11, 2000 2:21 PM
> Subject: RE: Application.variables vs local.variables
>
>
> | by checking for an application variable and setting the DSN to an
> | application scoped variable in the event that the variable does not
exist,
> | you require the CFAS to set the variable only every once in a while,
> rather
> | than everytime a page is requested. This is ideal from a performance
> point
> | of view.
> |
> | ~Simon
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
