[Seaside] WACurrentSession value is nil within a forked block

[Leandro Perez]

>
> > 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.
>
> Cheers,
> Lukas





Great Lukas thanks!
Leandro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20071105/84c00361/attachment.htm