[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 #8 by ramon.leon:
"Depending on what you need from the session, it would be a lot safer 
to pass in the current value of
whatever session data those processes need."

Actually, that's exactly what I did to get around this so I have no 
problem with that approach.  I just remember
being surprised by this way back when and I've had to explain it 
several times to others so I thought maybe there
was a simpler way to make this obvious to people.



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