Chris, I'm not trying to be misleading at all. In fact, I'm trying to be the
opposite. If you look over all the posts I've written on this, I've clearly
said the request scope is NOT a shared scope (which is why it doesn't need
to be locked). I was just trying to get the point across that request is NOT
tied to a single user, unlike client and session.
-----Original Message-----
From: Chris Bartley [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 5:57 PM
To: Fusebox
Subject: RE: Idea?
Oh, come on, Hal, that is really misleading. Sure, the ability to use the
request scope is available to all users (regardless of whether client or
session management is being used), but that does NOT mean that, if you and i
hit the same page at the same time, my request-scope variables will ever be
confused with yours.
Request-scope variables live only as long as a single HTTP request, and
belong only to that single HTTP request.
At 5:44 PM -0400 10/10/00, Hal Helms wrote:
>No, request is not tied to a specific user. If you doubt this, change your
>cfid or cftoken.
>
><cfapplication name="me" clientmanagement="Yes">
><cfset request.myName = "Hal">
>#request.myName#<br>
>
><cfset cftoken = "2555">
>#request.myName#
>
>In both cases, you will see "Hal"
>
>Hence, request is "available to all users".
----------------------------------------------------------------------------
--
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.
------------------------------------------------------------------------------
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.
