[Seaside] 'Clean' URLs in Seaside

Phil (list) pbpublist at gmail.com
Thu May 7 19:08:07 UTC 2015


On Thu, 2015-05-07 at 09:55 -0300, Esteban A. Maringolo wrote:
> The shortcoming of using _s in a cookie is that you cannot open a
> separate tab and start a new session. The session is "per browser"
> (UA). Which is commonplace behavior these days, but I don't think it
> will add much just moving the parameter from one place to another.

That's an excellent point and I'll keep it in mind.  For my current app,
I don't need to know much about a session other than as a way to tell
that one request is from a different person than another.  Even then,
it's fairly generic and anonymous (i.e. think user preferences rather
than shopping carts)

> You can have bookmarkable URLs in your app though, but even when
> Seaside supports that (via the #updateUrl: method), there is no
> framework to automatically generate RESTful URIs and route back the
> requests composing the component tree according to requested URL.

True, you give up automatic URL handling.  But for some apps, that's a
worthwhile trade-off without going the full RESTful route (at least as
described in the Seaside book)

> Regards,
> Esteban A. Maringolo


More information about the seaside mailing list