[Seaside-dev] about issue 103

[Philippe Marschall]

2008/8/2 Lukas Renggli <renggli at gmail.com>:
>> No, no, nothing obviously wrong with the approach, I think. I
>>  generally like the request context approach. I was just curious what
>>  the grand vision behind it was and 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.

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

Cheers
Philippe