[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 #3 by ramon.leon:
That's a nice idea, can that be added as an extension in the Seaside 
package with a comment explaining that
once you do this, you are now responsible for dealing with any 
concurrency issues that arise?  The fact is,
concurrent processing is sometimes necessary, despite Seaside wanting 
sessions to be single threaded.  There's
also need to be a #forkWithSessionAt: to allow setting the priority.



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