It seems to me that when an cfincluded page re-defines the value of a request-scoped variable, this is not something special/unique about request scope. This could happen in any other scope. What does appear to be special is custom tags. I guess the point here is that the custom tag writer could accidently CFSET the value of a request-scoped variable whose name is the same as a variable in the calling template, and thus give an unintended value to the request-scoped variable. Is this right so far? best, paul At 01:19 AM 10/9/00 -0400, you wrote: >Not just in custom tags, but in any included pages as well. > >-----Original Message----- >From: paul smith [mailto:[EMAIL PROTECTED]] >Sent: Monday, October 09, 2000 12:59 AM >To: Fusebox >Subject: RE: Idea? > > >I'm trying to understand how a request scoped variable that > >1. Is unique to a user, and >2. Dies with a new page request > >can have an unexpected value in other nooks and crannies in an >application. > >Is the *real* problem only with custom tags? > >best, paul > ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
