[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 #6 by ramon.leon:
Keep in mind that forking does not create concurrency issues, nor does 
sharing state, only mutating that state
creates the problems.  The background thread may just need access to 
application configuration information
which is hung off the session.



-- 
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