Please excuse the generalized questions, but I'm trying to hammer down some more standards for our apps in the CFMX era and I just want to make sure I'm doing the "right" thing (as if it were a spike lee joint):
Now that there is a lesser chance of actually corrupting the server while using the application scope in CFMX, how much can I legitimately put into the application scope and get away with? I've started putting all our global variables there now on our CFMX projects and I keep finding myself wanting to put more and more in there...such as menu structures, and giant permissions meta arrays, etc. I figure why write it on every call, when the variables are going to be the same on every request, that's what it for right? (And I'm still locking the sets for each group of variables with a name exclusive lock, but I'm not locking the reads.) But how much is too much? Is there any way to load test this? Is it better to write to a temporary (variables) scope that gets cleaned up on every request or to toss the variables into the application scope and have it hanging around waiting to be read? This is probably the start of a few questions...but this is the most important, so I'll see what I get back before I throw too much out there-> Tyler Silcox ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
