> Application scope only exists once per application. Session exists once > for each user. You might get away with bloated memory usage in > application, but if you are not careful what you place in session your > problem can very quickly multiply.
On that note I have a question - I am looking into building an app that my company will be selling to customers to use in a "shared" environment. It's starting out as a CMS but is going to include a LOT of user controls and module support. The idea is that each domain will have an Application name based on the domain which will then call a shared CFC to create a "memory cached" version of the site in the Application scope. Then, as the pages in the CMS are called the engine does not have to call out to the database, rather it simply references the version that is cached in the application scope. At least, that's the way I'm thinking of doing it... what I wonder is how the server performance will be with 100-150 sites running, each with their own application and different things going on. Understand, these are what I'd call mid-traffic sites but for the moment all brochureware. The point of my question - would it make more sense to have the necessary bits to connect to the database and pull the page content on request stored in memory or just have the entire page content already in memory after being loaded on the first page vistit when the application reloads? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:279357 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
