I've never used the server scope in apps, so it's not a question I can answer...perhaps others will chime in on this one.
And, as part of this situation, there are almost no variables that are shared between applications, so I don't see that there would be many variables to put into the server scope. Every site has its own database, paths, etc. Rick -----Original Message----- From: DURETTE, STEVEN J (ATTASIAIT) [mailto:[email protected]] Sent: Friday, February 18, 2011 10:11 AM To: cf-talk Subject: RE: Feedback on this approach to "many sites, one codebase" (MSOC) Probably a stupid question, but if the data was used across applications wouldn't it make sense to push it into the server scope? That would allow you to have one copy of the needed items, but still let you keep the applications separate. I know that a lot of the time having a different application name for each application while troubleshooting can be extremely helpful. I don't have a situation like this and I hardly ever look at the server scope, so I'm just asking because it will help further my knowledge. :) Steve -----Original Message----- From: Eric Cobb [mailto:[email protected]] Sent: Friday, February 18, 2011 9:15 AM To: cf-talk Subject: Re: Feedback on this approach to "many sites, one codebase" (MSOC) One thing you may want to take into consideration, if you plan on having many sites run through this codebase, is NOT giving each site a unique application name. (as in <cfset this.name = "#cgi.server_name#">). I once worked on a MSOC system that ran somewhere around 2700 websites, and each site had its own application name. So, every time we cached a CFC in the application scope, we had 2700 separate instances of it, even though they were all identical. We had 2700 "application.dsn" variables stored in memory, even though they were all identical. We had multiple CF servers each trying to store and manage the same 2700 separate applications, all of which were completely identical. And the worst part was, there was no passing "?reinit=1" if we made code changes and needed to reset the application scope, we had to restart each CF server and take all 2700 sites offline in order to reset all of the applications. To me, this always seemed inefficient, and a gross waste of CF processes and memory. Just some thoughts I wanted to throw out there. Definitely something to think about if you're planning on having a large number of sites on your system. Thanks, Eric Cobb ECAR Technologies, LLC http://www.ecartech.com http://www.cfgears.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:342429 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
