>Then the question becomes, why even bother scoping the dsName to
>application. Why not just set variables.dsName in application.cfm?
That's exactly what I do. I have a constants file that I include in my
Application.cfm file and then just reference them. The overhead of creating
them on each request (and yes, I have stress tested this!) is so minimal
that it's worth it to me. I save lines and lines of locking code by doing it
this way.
However, that being said, CF MX has eliminated the need to lock in
situations *other than race conditions* (i.e., setting or reading a
variable). In this case, you can eliminate even that slight overhead
mentioned above by just using application variables.
My rule of thumb has become:
<cfif CF version EQ "CFMX">
use application vars, and lock only for race conditions
<cfelse>
set vars on each request via an include file in Application.cfm and
avoid the locking mess
</cfif>
Regards,
Dave.
______________________________________________________________________
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
