> I wish Allaire/Macromedia would address the problem of requiring > high level > programming locks for session and application variables and place > that code into the interpreter where it belongs.
I for one am glad Allaire/Macromedia has *not* done this. I like my applications to run fast. Automatic locking (which is available for reads BTW, and on reads and writes in session scope), slows things down because it opens and closes locks as needed, and in most cases more frequently than it should. -Cameron -------------------- Cameron Childress elliptIQ Inc. p.770.460.1035.232 f.770.460.0963 -- http://www.neighborware.com America's Leading Community Network Software > -----Original Message----- > From: UXB Internet [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 28, 2001 1:27 PM > To: CF-Talk > Subject: RE: Session variables > > > <cf_rant> > > I wish Allaire/Macromedia would address the problem of requiring > high level > programming locks for session and application variables and place > that code > into the interpreter where it belongs. > > If you ALWAYS have to lock session and application variables then the code > to do so should part of the core cfml program and not in the scripting. > > In my opinion this is an aggravating flaw in an otherwise outstanding > product. > > </cf_rant> > > Sorry about that folks. > > > Best regards, > > Dennis Powers > UXB Internet > (203)879-2844 > http://www.uxbinfo.com/ > > -----Original Message----- > From: Dave Watts [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 27, 2001 3:51 PM > To: CF-Talk > Subject: RE: Session variables > > > > You should allways use CFLOCK when dealing with sessions. > > > An alternative is setting the Single Threaded Sessions in > > > the CF Administrator. > > > > I don't know if this is an optimal solution, but I always transfer > > all session variables to the request scope - inside a CFLOCK - > > in application.cfm. That way there's just one locked section of > > code for session variables and you don't have to remember to > > use a lock every time, just to use request.variableName instead > > of session.variableName. > > It's been our experience that this method doesn't work well if you're > storing any significant amount of data in the session or > application scopes. > It may work during functional testing, but generally fails miserably under > load. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > voice: (202) 797-5496 > fax: (202) 797-5444 > > ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona 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
