[Seaside-dev] Seaside 2.8 release planning

[Philippe Marschall]

2007/10/15, Lukas Renggli <renggli at gmail.com>:
> > > > http://bugs.squeak.org/view.php?id=6527
> > > > I don't consider this critical. It affects only the url which is first
> > > > displayed when a new session is created. #initialRequest and
> > > > #updateUrl: still work and any following "page" will have the
> > > > paramters.
> > >
> > > The problem is that the #initalRequest: thing only happens afterwards
> > > and therefor all this data gets lost. This is a reason why Session
> > > cookies and Pier do not work together. A pity it is that hard to fix
> > > ...
> >
> > Can you have a look at Seaside2.8a1-pmm.504? It's hackish but at least
> > the WABrowserExample works for me.
>
> This only solves part of it: the parameters, but not the path elements
> of the URL with is tricky.

Right, I missed this one.

> Maybe the URL parsing code would help here?

String to url conversion in general would be great. Also some
convenience methods to calculate the "difference" between two urls.
Bug what we want in the end is the url we build in
WASessionContinuation >> #url. I mean in general people could do more
than just adding path elements and paramters. The could change the
port, protocol or what ever.

Cheers
Philippe