[Seaside-dev] Issue 98 in seaside: Forking a background process
loses access to the current session
codesite-noreply at google.com
codesite-noreply at google.com
Sun Jul 13 18:57:25 UTC 2008
Issue 98: Forking a background process loses access to the current session
http://code.google.com/p/seaside/issues/detail?id=98
Comment #10 by ramon.leon:
Agreed, then there'd be a standard way and known risks. Maybe even
document how to access the sessions
monitor, which is currently not publicly accessible so the thread could
safely open a critical section and modify
state if necessary, or maybe pass the session a block to execute in a critical.
--
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
More information about the seaside-dev
mailing list