On Fri, Dec 17, 2010 at 8:32 AM, Jason Allen <[email protected]> wrote:
> I guess my question more than anything, is that is there a problem > with potentially have a HUGE session variable with potentially tens of > thousands of characters? > You probably know what my answer is going to be. :-) It depends. In and of itself, no--fill up your session to your heart's content until you run out of memory. Could it be an issue with a large number of users? Sure, but that's true of any app at a given load, and you don't know what that is for your app unless you do some capacity planning and load testing. To put it another way, there is no way to answer this question accurately without any metrics. > > Also, is there a problem with naming the session variable uniquely > each time? This way if the user is working on several pages, I > wouldn't have one page being created overwrite the session variable of > another. > Nope, unique session variable names will just mean they're separate session variables, and of course each one takes up some RAM. -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
