[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 #1 by philippe.marschall:
Putting the session inside a component doesn't sound like a good idea. 
A better way
of working around it is IMHO

| session |
session := self session.
[ WACurrentSession use: session during: [ actual work ] ] fork

This can easily be generalized into something like:
BlockContext >> #forkWithSession

Please note however that accessing session from forked processes has 
some serious
threading issues because there are now two Process accessing the same 
object. The
Seaside process and the forked 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