Newer releases of Seaside come with different session tracking
strategies, you could use WACookieIfSupportedSessionTrackingStrategy
With Mariano Martinez Peck we discussed (and he implemented) a mix of
Cookie and localStorage to enforce different sessions in different
tabs of the same browser.
Esteban A. Maringolo
El mar., 26 feb. 2019 a las 18:32, Cyril Ferlicot
(<[hidden email]>) escribió:
> On Tue 26 Feb 2019 at 20:41, Esteban Maringolo <[hidden email]> wrote:
>> You can use a different session tracking strategy, that will keep
>> track of the session (`_s`) identifier.
>> For the continuation (`_k') there is no way I know to avoid including
>> it in the URLs, unless you always start fresh.
>> What you might want is to have "clean" URLs, for that, refer to this
>> never aging article by Ramon Leon:
>> http://onsmalltalk.com/clean-urls-in-seaside >
> I am also interested in this and I don’t know enough cookies management to do it. (At least, I don’t have the time to learn for now :( )
> This tutorial is out of date and not applicable in the current Seaside. So, if someone has an equivalent for the current Seaside version it would be awesome!
>> Esteban A. Maringolo
>> seaside mailing list
>> [hidden email] >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >
> Cyril Ferlicot
> https://ferlicot.fr > _______________________________________________
> seaside mailing list
> [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
If you don't need you want the state snapshots ("back button support")
you could get rid of the _k. You would have to introduce a mechanism
to to remove the old callbacks to avoid memory leaks, this could
probably be done in the "continuation".
On Tue, Feb 26, 2019 at 8:41 PM Esteban Maringolo <[hidden email]> wrote: