You could - however, unlike exception handling, process-local variables are not part of ANSI. Which means it's a safer choice for Seaside from a portability POV.
Speaking of which, referring to my last post when Danie raised the issue, is there any reason we don't copy the process environment when forking? Cheers, Henry On 18. juli 2011, at 16:47, Igor Stasenko <[email protected]> wrote: > For instance, in Seaside (if i remember correctly) it creates a > separate process for handling request. > And so, for dynamic variables you can use a process-specific storage , > provided by > Process>>environmentAt: and environmentAt:put:, rather than using > exceptions to access dynamic variable values. > Like that, you don't need to use exceptions and moreover it will work > much faster, because unwinding stack each time you accessing the state > is costly! >
