Hopefully someone can answer two newbie questions ..
I've read a few blog entries about storing general utility components in the
application scope so they can accessed anywhere within the application.
<cfif NOT isDefined("application.Utilities")>
<cflock scope="application" type="exclusive" timeout="10">
<cfif NOT isDefined("application.Utilities")>
<cfset application.Utilities = createObject("component", "Utilities")>
</cfif>
</cflock>
</cfif>
<cflock ...>
<cfset Request.Utilities = application.Utilities>
</cflock>
It makes sense to instantiate the component once and store it in the
application scope, but 1) why copy it back into the Request scope ? So it will
be available to custom tags? 2) Why is it necessary to use a lock when copying
the component into the request scope?
---------------------------------
No need to miss a message. Get email on-the-go
with Yahoo! Mail for Mobile. Get started.
You are subscribed to cfcdev. To unsubscribe, please follow the instructions at
http://www.cfczone.org/listserv.cfm
CFCDev is supported by:
Katapult Media, Inc.
We are cool code geeks looking for fun projects to rock!
www.katapultmedia.com
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
