Hi all.
First of all, if there is a good treatise on this subject, could
someone kindly point the way? 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?
Is it a way to have manually managed global variables within an
application without resorting to locks and CF sessionids??
Based upon this threads discussion, it would seem that you would have to
create a naming convention for use within a http page request.
Thanks for the insite! [to riot]
slightly confused,
Steve
p.s. Why does locking not play a part in these variables? Or does it?
At 11:43 AM 10/8/2000 -0700, Nat Papovich wrote:
>Because request is friggin global in scope! That is mucho dangerous. I would
--
Stephen Garrett
GPS
[EMAIL PROTECTED] (360) 896-2714
ICQ# 10776767
------------------------------------------------------------------------------
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.
