>One thing to keep in mind, if you do not have a *unique *ApplicationName on >your server, then the variables could be shared w/another application--which >is especially dangerous on shared hosting. > >I've seen people roll out an application w/a common ApplicationName like >"MainApp" and have issues w/their App scope being shared w/another >application that also used a name of "MainApp". Same thing happens if the >Application.cfc/cfm doesn't define a ApplicationName. > >IMO, the safest thing you can do is name define ever ApplicationName with a >hash of the current directory path: > ><cfset this.name = hash(getDirectoryFromPath(getCurrentTemplatePath())) /> > >That way you can use the same code w/every Application.cfc, but your >virtually guaranteed to have a unique ApplicationName. > >-Dan >
Dan - That's a good tip but the app name is unique and I've verified that there are no unintended conflicts by dumping the application object's variables. (But, yes, I'm on shared hosting - meant to say that.) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:343365 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
