>
>> "?_k=RLuphTHk&_s=IkufVPbXiraGKGSB" on the url - maybe by using a
>> cookie ? I'd like to get a readable url and hide what is not
>> human-understandable...  (Why ? In fact, I'm studying the use of the
>> url box as a kind of command line for webpage seen as object
>> "www.foo.net/myappli render: 'hello world'")
>
> Seaside is different. You can use Seaside to do that kind of things,
> but that is not the idea behind the framework: Seaside is all about
> hiding the low-level aspects of URLs, HTTP-Requests, HTTP-Responses,
> etc. Seaside provides you with tools to easily model flows of pages,
> to compose and reuse widgets, to build state-full web applications,
> etc.
>
> Still it is possible to move the session key into a cookie, by setting
> the configuration option of the application, though most people don't
> bother about this. Seaside is strong at building highly interactive
> web applications, not at building static web sites with REST-full
> URLs.
>
Those session keys can bother if someone wants to add the www into the
favourites and the browser saves the URL with the key. You must delete
the key from the URL manually, and this does not have to be obvious for
everyone.

Elod