I think they are referring to this way of 'stealing' data:

<cfapplication name="some other guys apps">
<cfset myCopy = duplicate(application)>
<cfapplication name="original name of application">

All this will do is copy over the other app's application data. I
_think_ I wrote a UDF for this on cflib.org.

Defintely _NOT_ a big fat hairy deal.

========================================================================
===
Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc
(www.mindseye.com)
Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia)

Email    : [EMAIL PROTECTED]
Blog     : www.camdenfamily.com/morpheus/blog
Yahoo IM : morpheus

"My ally is the Force, and a powerful ally it is." - Yoda 

> -----Original Message-----
> From: Ben Forta [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, July 03, 2003 11:39 AM
> To: CF-Talk
> Subject: RE: CrystalTech says ALL variables must be locked
> 
> 
> >> If not, other sites can steal them
> 
> I have no idea what that even means!
> 
> Regardless, it is worth noting that problems caused by the 
> lack of locking (CF4.x and CF5) can be slow and gradual. On a 
> shared box you may see memory corruption problems (do to the 
> lack of locking) even if your app has no shared scope 
> variables at all. How? If another app on the box uses shared 
> scopes and fails to lock code. All CF apps share the same instance.
> 
> Which is why CFMX on J2EE is so compelling. Each app runs in 
> its own safe little world.
> 
> --- Ben

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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
                                

Reply via email to