[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

New issue report by ramon.leon:
Sessions are implemented with dynamic variables that you lose access to 
when you fork a block and
try to do anything asynchronously.  Dynamic variables don't inherit 
their parent processes variables
because Squeak processes don't keep track of the parent process.

Hacking around it isn't too difficult if you expect it, just cache the 
session object in your
WAComponent subclass so every call to self session doesn't attempt to 
use the dynamic var, but is
there some cleaner way to do this, perhaps fixing dynamic vars 
themselves, or creating a special
dynamic var for seaside that remembers it's parent process and just works?



Issue attributes:
	Status: New
	Owner: ----
	Labels: Type-Defect Priority-Medium

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