The session scope is a memory variable as you know, and therefore affects the whole system, and any other applications that are running on that system. When you use an exclusive lock, you are infact tying up that small portion of system ram until which time that lock releases and obtains another lock.
Doug B. ----- Original Message ----- From: "James Holmes" <[EMAIL PROTECTED]> To: "CF-Talk" <[email protected]> Sent: Sunday, December 03, 2006 8:04 AM Subject: Re: memory issue with session scope in custom tags? > No, because a session lock works only for the session in question, not > the whole server. > > On 12/3/06, Doug Brown <[EMAIL PROTECTED]> wrote: > > Well, I would imagine that they are saying this for good reasons. Most of us > > as developers do not see the impact of exclusive locks, or at least not > > enough to notice a difference in performance. It is possible that as a > > hosting company running several shared servers that the impact would be far > > greater. > > -- > CFAJAX docs and other useful articles: > http://www.bifrost.com.au/blog/ > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:262663 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
