i believe that Request variables also belong in that upper list. in answer
to your question about a difference in scoping vs. not scoping in the lower
list, you can choose to use the prefixes or not. some people purposely do
not scope their variables to make their templates more flexible (allows them
to use the same template to either accept info from, let's say, both url and
form variables). but the recommendation from allaire is to scope the
variable because:
1. it avoid confusion for the developer (sometimes you may have variables of
the same name from different scopes on the same page)
2. if avoids confusion for the cf app server, too (if you have to variables
of the same name but different scopes on the same page and you don't scope
the variables, then it process the variables in the "scanned order" you have
listed below - whichever one it hits first is the one that is used)
3. supposedly, there is a performance gain if you scope the variables 'cause
cf doesn't then have to scan for you.
-emily
>variable scope required:
> 1) Server
> 2) Application
> 3) Session
> 4) Attributes
> 5) Caller
>variable scope not required, scanned in the following order:
> 1) local (i.e. Variables)
> 2) CGI
> 3) File (???)
> 4) URL
> 5) Form
> 6) Cookie
> 7) Client
>- is there any difference in using Variables.x and not using it?
>- what are File variables?
>---------------------------------------------------------------------------
---
>Archives: http://www.eGroups.com/list/cf-talk
>To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
>
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
