[Seaside-dev] about issue 103

[Julian Fitzell]

On Sun, Aug 3, 2008 at 3:42 AM, Philippe Marschall
<philippe.marschall at gmail.com> wrote:
> 2008/8/2 Lukas Renggli <renggli at gmail.com>:
>>>  I guess I was trying to see how
>>>  this was better than walking up the #parent chain (or if you were
>>>  intending to get rid of #parent).
>>
>> That's true, since 2.8 there is the possibility to walk up the parent
>> chain. Now I don't see anymore why we wanted to remember all the
>> request handler?
>
> Well we need to know the current one to know where to start. It would
> be possible to know just the starting point as long as everything is
> restored after it is done.

Ah yes, good point. And that pretty much requires a block wrapper to
ensure anyway.

> IIRC originally the idea came from having nested contexts (dispatcher
> context, application context, session context, request context) but we
> settled for the last one and a stack because of simplicity and it fit
> our needs (for now).

That makes my head swim a little bit... :) sounds like the principle
of simplicity will serve us well here for the moment.

thanks for providing some background,

Julian