I say this because I rarely see problems due to oversized application scope variables. With a single application scope per application, you only get 1 'chunk' of data where you get a chunk of data per session. On the other hand, if your problems started with the addition of data to the application scope then it's definitely the place to start. Have you dumped it out to see what it actually contains vs. what you think it should contain?
> However, (and this may sound completely foolish), why do you > > say the following (emphasis added): > > what is stored in the application scope /(which doesn't really > matter much)/ and what is stored per user session /(which can be > critical)/. > > > What makes one more critical than the other? I'm asking because the > application services have crashed a couple of times recently and we'd > > just started storing a structure in the application scope that my > friend > thinks might be too big. I'm not convinced of that however. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJQ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:279289 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
