This post is more to what Jeffry was replying too:-) Ok, I created a membership system. The system that I use requires client variables over session, but uses the request variable to say who is logged in, what policy they have etc.
Now if I write a serious of custom tags, I could pass this along via an attribute. But why should I waste server memory by duplicating the space needed in ram to keep variables when it is already stored in a variable. Think about that for a moment, then you'll understand that if you don't have control of the server this can become a critical thought to your application. -----Original Message----- From: Jeffry Houser [mailto:[EMAIL PROTECTED]] Sent: Thursday, 27 June 2002 11:23 PM To: CF-Talk Subject: RE: What is the best variable scope? Do you have examples and / or numbers? At 06:50 AM 6/27/2002 +0000, you wrote: >While I agree in principle with your sentiments here, the request scope can >help out in some cases with performance. > > Actually, I prefer not to use the request variable scope. > > Parameter passing is important part of custom tag re-usability. Writing > >custom tags that are based on 'global' variables (I.E. the request scope is > >global to the current request) violates the re-usability constraint. > > The only reason I see for the request scope over the variables scope is > >to avoid parameter passing. ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. 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
