> You guys have really lost and confused me on this thread. Why are
> you locking session variables per user??? I would understand in
> the case of a machine having a session with another machine but
> a session for a specific user keeps other users out by design.
> And given that CF processes commands in sequence you wouldn't
> have to worry about locking a session var unless you are going
> to access it immediately and are concerned that your previous
> write might not be finished in time. Locking variables is
> relatively new to me, so I would like to understand them further,
> so if I'm completely missing the ball park here, please let me know.
Common sense would lead to the conclusion you've reached. Unfortunately,
this problem currently falls outside the realm of common sense. There are
several things which might cause multiple concurrent page requests from the
same user - framesets, the user opening another copy of the browser, the
multithreaded nature of browser request processing, heavy load on the server
causing wacky and essentially unexplainable problems. So, you'll need to
lock your session variables too.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
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.
