[Seaside] Authorization, cookies, etc.

[Avi Bryant]

On Mon, 17 Jun 2002, Kamil Kukura wrote:

> I was thinking about multiple entry points. That is, there would be
> 'root' as the main entry point and then there would be dictionary of
> aString -> aClass so that link http://somewhere/seaside/theapp/foobar
> could be resolved by mapping:
>
> 'foobar' -> IAFooBarComponent

In general I don't see much difference between this and between having
multiple applications configured - you can use /seaside/theapp-foobar
instead of /seaside/theapp/foobar.

However, if you do want to allow that, you can play with adding a
handleFoobar method to your session class, to go with handleView,
handleProfile, etc.  That is, the segment of the url after the app name is
converted into a method call to session.