re:concurrency and sessions
re:concurrency and sessions
- Subject: re:concurrency and sessions
- From: Jonathan Rochkind <email@hidden>
- Date: Tue, 22 Jul 2003 09:59:09 -0500
At 06:33 PM 7/21/2003 -0700, Ben Trumbull wrote:
True. Only one thread may check a session out of the session store at a
time. Sessions are NOT re-entrant.
However, there is nothing useful you may assume/conclude/derive from this
while interacting with EOF (like editing contexts). In other words,
concurrent request handling is only relevant to the WOF layer classes
(sessions, components, direct actions, etc)
Yes, thanks for the warning. As I am currently working on some general
purpose code for locking additional ECs used in a session (peer or nested),
my code kind of exists in between the WOF layers and the EOF layers. The
code is called through the WOF layers, but of course locks and unlocks ECs
which effects the EOF layers. So I'm needing to think about both to make
sure I don't get deadlock, and lock everything appropriately. Knowing that
Sessions are not re-entrant makes the job significantly easier, I think.
--Jonathan
--
-Ben
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.