Hi all: I always hear this issue discussed, and I have my own ideas, but I wanted to know what others think because I don't know that I've reached any conclusions as to what method is the best. I will not say how I do it, so as to promote unfiltered views. :-) There is an application. Users can log in to it. There are obviously variables that must persist (e.g. username, password). SESSION SCOPE If we use session variables, I always hear the argument that when it comes time to scale (i.e. a server farm), it's a headache because the session scope is server-dependant. Is this the only real reasoning behind not using the session scope? Aren't there solutions that make this a non-issue? HIDDEN INPUTS If we use hidden inputs, scalability isn't an issue, but we have to keep track of all the variables manually. We could write a control that handles this for us. But then there's the issue with timing out the session. We could solve this using some database table with some ID and timestamp of last post solution. But it gets complex. What are some of your thoughts? What is the best way to go about this? --Dave ################### David Notik Digital202, LLC Imagination gone digital. Web: <http://www.digital202.com/> www.digital202.com E-mail: <mailto:dave@;digital202.com> [EMAIL PROTECTED] Office: (206) 575-1717 Mobile: (206) 351-3948 ###################
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com
