Any app can fail under load. I guess I think it's not appropriate to make blanket statements about the technique. Certainly an app using a small amount of session data, but with a large amount of users, is, roughly, equiavalent to a small amount of users and large session strcutures. (Ok, maybe not equivalent, but you get the idea.) Under that kind of thinking, my original warning about a large structure would apply then.
(Just my 2 cents.) ======================================================================= Raymond Camden, Principal Spectra Compliance Engineer for Macromedia Email : [EMAIL PROTECTED] Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > -----Original Message----- > From: Dave Watts [mailto:[EMAIL PROTECTED]] > Sent: Saturday, April 27, 2002 4:08 PM > To: CF-Talk > Subject: RE: Session variable question > > > > Who said it was terribly inefficient? Sure, if your session > > scope contains 500 variables, it's probably a bad idea to > > always copy it, but I think that for _normal_ usage, doing > > a request.session = duplicate(session) (within a cflock of > > course ;) will not be harmful at all. > > I think I've said it's terribly inefficient, or words to that > effect. On > more than one occasion, this approach has failed spectacularly within > production applications under load testing, in my experience. Beware. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > voice: (202) 797-5496 > fax: (202) 797-5444 > > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
