[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 #4 by ramon.leon:
What I use it for right now is kicking off about 10 background threads 
to go fetch hotel rates for a property
widget and upon finding that rate ajax in the price so I can render the 
page immediately while waiting for rates
to come back whenever they come back.  I can't do this on the main 
thread because it serializes the requests.  I
don't actually need anything right now because I handled it a different 
way, but I recently helped Carl Grundel do
some stuff on Run Basic and he ran into the same issue, Smalltalker's 
are going to use #fork and they don't
expect to lose access to self session when they do so.



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