OK, I know everyone is going to hate me, but I think I can give the most concise
definition of a request variable yet. Think of it as a challenge in English and
efficiency of communication!
Here's my one line definition of request variables:
Request variables and local variables (scope = VARIABLES) act and can be treated in
EXACTLY THE SAME WAY, with the exception that request variables can go across the
<CFMODULE/CUSTOM TAG> boundary, while local variables are "isolated" to the page and
<CFINCLUDE>.
Local variables: die with the page request
Request variables: die with the page request
Local variables:
available in all <CFINCLUDED> code
Request variables:
available throughout the cascading chain of <CFINCLUDE> AND <CFMODULE> code.
If you know how local variables work, then you know how request variables work!
STOP THINKING SO HARD!
(but please do yell at Allaire for the lack of documentation that caused your
headache!)
At 12:15 PM 10/8/00 -0700, Stephen Garrett wrote:
>? I have seen discussion on the subject,
>but have not seen definative reasons why you would want to use these,
>excepting as perhaps a sort of global variable within a page request
>scope, that are available to all tags/modules as a back door communication
>mechanism.
>
>When I first heard of request variables, I had assumed they were a variation
>of session variables. But hearing within this thread that they are global
>across all simultaneous page requests (where there could be dozens or
>hundreds of simultaneous http requests in process), I am wondering if
>someone could shed light as to why you actually want to use these things?
================================================
Douglas M. Smith - Database Architect/Web Integration Specialist
TeraTech - Tools for Programmers(tm)
[EMAIL PROTECTED]
------------------------------------------------------------------------------
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.
