I actually disagree; I started using the request scope when it was introduced. I have no problems with it; however I will say that you need to be extremely careful when it comes to memory.
For example I see from the content so far that a lot of people copy variables to the request scope!! Why, this is one reason I HATE spectra the over usage of variables eats through memory like a hot cake. My best suggestion is to adopt the same principle as C/C++ has with structures etc. Pass them along, as a structure this way there is only every one copy and it's easier to see the structure being created and being passed than trying to debug where the problem came from when created elsewhere. Just my experience so far!! Or in the case of my membership system, it requires one structure that is initialized at runtime which places the information into this request structure. I do this because it easier than passing this structure over and over again. But the information is basic and kept to a minimum, otherwise I use normal variables or client variables. -----Original Message----- From: Neil Clark [mailto:[EMAIL PROTECTED]] Sent: Thursday, 8 November 2001 11:56 PM To: CF-Talk Subject: RE: Session variables Good option, but the request scope is a memory killer - Spectra is based on it and can suffer really bad performance at times. Neil Team Macromedia ______________________________________________________________________ Get Your Own 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=coldfusionb 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
