[Seaside-dev] Issue 98 in seaside: Forking a background process loses access to the current session

[codesite-noreply at google.com]

Issue 98: Forking a background process loses access to the current session
http://code.google.com/p/seaside/issues/detail?id=98

Comment #2 by jfitzell:
This is, of course, tricky because part of the contract seaside offers 
developers is
that concurrent access to the session (and therefor to a request 
context) is
prevented. Much of the session state could have changed by the time 
your new process
gets to using it. Obviously, you could be blocking the request handling 
process and
creating several other processes that are only reading the session 
though (to run
several pieces of work in parallel).

In 2.9, which uses process variables instead of dynamic variables, this 
is probably a
little more easily accomplished. I already did it in the specific case 
for the
Debugger but it could be generalized so that a single call on 
BlockContext would copy
the value of all process variables onto the new process.



-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings