> I got a tip previously on cf-talk that advised me to do
> this in my application.cfm:
>
> <!--- Page By Page Session Variables --->
> <CFIF IsDefined("Session.Collections")>
> <cflock scope="session" type="readonly" timeout="20">
> <cfset request.session = duplicate(session)>
> </cflock>
> </CFIF>
>
> <!--- Page By Page Application Variables --->
> <cflock scope="application" type="readonly" timeout="20">
> <cfset request.application = duplicate(application)>
> </cflock>
>
> Is this good or bad? (My sites typically have between 10
> and 200 connections.)
In general, I'm not a big fan of this approach, which is basically intended
to keep you from having to do the actual work of using CFLOCK tags within
your code. In my experience, this causes significant overhead within the
application.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Signup for the Fusion Authority news alert and keep up with the latest news in
ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
