I have come across some similar code also, moving variables scope into sessions and back again for no reason. if the data has no reason to persist past the request then there is no reason to put it in session scope. the primary reason for doing it with forms is to persist the form data so users can come back later and their data is still there, such as when a form is split across multiple pages..
perhaps you could just ask him why he is doing it. On Tue, Jan 31, 2012 at 8:24 PM, Maureen <mamamaur...@gmail.com> wrote: > > I think I ran across that guy once (lol). IMO, loading anything other > the absolute minimum required info to identify a unique session into > session variables is bad coding practice. > > On Tue, Jan 31, 2012 at 8:01 AM, Robert Harrison > <rob...@austin-williams.com> wrote: > > > > I'm an old school programmer who watches every bit and byte and really > practices resource management in my coding practices. > > > > I've got a new programmer working for me (on contract) and I'm finding > he's using session Vars all over the place. He creating session Vars on > forms that have a hundred fields, he putting arrays into session Vars, etc. > I just went through a few of the programs he wrote and used them, then I > dumped my session vars and found I had over 250 session vars from just > using a few programs. Considering the site has over 1,000 users on it at > any given moment, I'm very concerned about this practice. > > > > Am I nuts, or is this just bad? > > > > Thanks, > > Robert > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:349689 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
