[Seaside] WACurrentSession value is nil within a forked block
renggli at gmail.com
Mon Nov 5 15:03:16 UTC 2007
> Is this behavior correct?
Yes, given the current implementation this behavior is totally correct.
> should the session be nil inside a forked block?
You can avoid your particular problem like this:
session := self session.
[ WACurrentSession use: session during: [ ... ] ] fork.
> if so, why?
WACurrentSession uses the exception handling (the execution stack) to
determine the current session. A forked block has a new stack and
looses this information. The package DynamicBindings provide some
tools to make similar things work across process boundaries,
unfortunately this is not really platform independent.
More information about the seaside