[Seaside] Using meaningful links

Norbert Hartl norbert at hartl.name
Mon Jun 6 10:53:49 UTC 2011

Am 06.06.2011 um 12:20 schrieb Julian Fitzell:

> On Sat, Jun 4, 2011 at 12:17 AM, Norbert Hartl <norbert at hartl.name> wrote:
>> Am 31.05.2011 um 15:00 schrieb Julian Fitzell:
>>> Hi Scott,
>>> Sure. There are a number of possible approaches to this, including
>>> using a RequestFilter around your application, registering a bunch of
>>> "redirection handlers" or (even real applications that share
>>> components with your main system), or just implementing
>>> #initialRequest: on your root component to parse the URLs.
>> I think it was asked before: What would be an appropriate way of injecting state generate by a filter into the application served by the handler? If I add a request filter that determines some things from the url I might set some things that are evaluated by the application to display certain things. Is there a nice way of doing?
> Hi Norbert,
> I'm not sure if I'm understanding your question correctly, but it
> sounds like your filter could store something in the property
> dictionary of the RequestContext for later filters to find? Another
> option is to use a dynamic variable or you could walk the handler
> stack in the request context looking for the filter and ask it
> directly.

It seems you understood perfectly what I was trying to ask. I myself thought about walk the handler chain to figure out things but somehow I felt this is not the best thing to do. Dynamic variable is indeed an idea I didn't think of. Thanks for that.
The property dictionary of RequestContext is what I was looking for. That is the missing link (and I didn't know it exists).



More information about the seaside mailing list