request scope is just for people who either don't understand parameter
passing or don't like writing "stand-alone" re-usable modules. :-) I
rarely use the request scope.
The current project I am working on we made the decision to use the
application scope. This is because they are loading the configuration info
from an XML document. In that case, storing it in memory is better than
re-loading a file on every page access.
>Subject: Application vs Request scope
>From: "Chris Alvarado" <[EMAIL PROTECTED]>
>Date: Thu, 22 Apr 2004 15:27:31 -0500
>Thread:
>http://www.houseoffusion.com/cf_lists/index.cfm/method=messages&threadid=32091&forumid=4#161044
>
>Hello all,
>
>
>
>I've been doing CF development for quite some time and as such im fairly
>set on the way I do things. However I just had a debate with another
>developer regarding which scope was proper for setting application wide
>variable (such as DSN names, file paths etc) in regards to locking /
>efficiency etc.
>
>
>
>What is everyone's preference and why?
>
>
>
>I typically use the application scope with proper locking during
>declaration. . .
>
>
>
>Is that the "correct" way or is request scope the preferred method and
>why?
>
>
--
Jeffry Houser, Web Developer, Writer, Songwriter, Recording Engineer
<mailto:[EMAIL PROTECTED]>
--
AIM: Reboog711 | Phone: 1-203-379-0773
--
My Books: <http://www.instantcoldfusion.com>
Recording Music: <http://www.fcfstudios.com>
Original Energetic Acoustic Rock: <http://www.farcryfly.com>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
