Hi Emily,
That explanation makes a lot more sense to me - thank you.
We're not using frames at all, so that issue does not arise, but the
customer reload / refresh does, so we will have to make sure our code is
robust enough to handle that.
Alan
-----Original Message-----
From: Emily B. Kim <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, July 13, 2000 5:32 PM
Subject: Re: Session variables
>> On session variables, they are only related to the session, so no matter
how
>> many users you have on line only the current session can be doing
anything
>> to the 'instances' of session variables that belong to it. Again,
therefore,
>> I can't see why you'd need to lock accesses to them. We don't use
'server',
>> so I have no comments about those.
>
>here's an excerpt from the allaire kb article on locking:
>http://www.allaire.com/Handlers/index.cfm?ID=14165&Method=Full
>
>*******************
>It is easy to imagine that an application with many users (browsers) may
>be trying to read and/or write server and application variables at the
>same time, but it's not so evident with session variables.
>
>Session variables are per browser session, so how can a browser request
>attempt to access the same variable at the same time?
>
>If you understand the way that browsers work, then you know that they
>can have several simultaneous threads between the browser and the
>server. This makes processing much faster, since the browser can get
>many of the page resources (images, framesets, etc.) at the same time
>instead of one by one. Most of today's browsers have 4 simultaneous
>threads going against the web server at the same time. (AOL browsers
>only use 2.)
>
>Since ColdFusion is usually set up to handle many requests from the web
>server at the same time (using the Simultaneous Requests setting in the
>ColdFusion Administrator), it is also possible that the simultaneous
>browser requests are being processed at the same time by ColdFusion.
>Therefore, it is possible that more than one page in a frameset be
>processed at the same time. If those pages all access shared memory
>variables, it is possible to cause a collision when processing, even
>within a single session.
>
>Also, if a user becomes impatient for a single page load and hits the
>reload/refresh button, it is also possible that the same page be
>accessed twice and simultaneously. Therefore, any access to shared
>variables is also a problem.
>*********************
>---------------------------------------------------------------------------
---
>To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk
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/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
