Keeping _s and _k in cookies

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Keeping _s and _k in cookies

sergio_101
Years ago, when I was running a different project, there was an option to keep this variables in a cookie, and they would not show up on the URL..

I was wondering if this is still possible, and how you go about doing it.

Thanks!



----
peace,
sergio
photographer, journalist, visionary


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Keeping _s and _k in cookies

Esteban A. Maringolo
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

Regards,

Esteban A. Maringolo

El mar., 26 feb. 2019 a las 15:22, sergio ruiz
(<[hidden email]>) escribió:

>
> Years ago, when I was running a different project, there was an option to keep this variables in a cookie, and they would not show up on the URL..
>
> I was wondering if this is still possible, and how you go about doing it.
>
> Thanks!
>
>
>
> ----
> peace,
> sergio
> photographer, journalist, visionary
>
> Public Key: http://bit.ly/29z9fG0
> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> http://www.codeandmusic.com
> http://www.twitter.com/sergio_101
> http://www.facebook.com/sergio101
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Keeping _s and _k in cookies

CyrilFerlicot


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

Hi,

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! 




Regards,

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
Reply | Threaded
Open this post in threaded view
|

Re: Keeping _s and _k in cookies

Esteban A. Maringolo
Newer releases of Seaside come with different session tracking
strategies, you could use WACookieIfSupportedSessionTrackingStrategy
or WACookieOnlySessionTrackingStrategy.

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.

Regards,

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
>
>
> Hi,
>
> 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!
>
>
>
>>
>> Regards,
>>
>> 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
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Keeping _s and _k in cookies

sergio_101
Okay! I am gonna try this…


On February 26, 2019 at 5:09:53 PM, Esteban Maringolo ([hidden email]) wrote:

Newer releases of Seaside come with different session tracking
strategies, you could use WACookieIfSupportedSessionTrackingStrategy
or WACookieOnlySessionTrackingStrategy.

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.
----
peace,
sergio
photographer, journalist, visionary


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Keeping _s and _k in cookies

Philippe Marschall
In reply to this post by Esteban A. Maringolo
Hi

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".

Cheers
Philippe

On Tue, Feb 26, 2019 at 8:41 PM 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
>
> Regards,
>
> Esteban A. Maringolo
>
> El mar., 26 feb. 2019 a las 15:22, sergio ruiz
> (<[hidden email]>) escribió:
> >
> > Years ago, when I was running a different project, there was an option to keep this variables in a cookie, and they would not show up on the URL..
> >
> > I was wondering if this is still possible, and how you go about doing it.
> >
> > Thanks!
> >
> >
> >
> > ----
> > peace,
> > sergio
> > photographer, journalist, visionary
> >
> > Public Key: http://bit.ly/29z9fG0
> > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> > http://www.codeandmusic.com
> > http://www.twitter.com/sergio_101
> > http://www.facebook.com/sergio101
> > _______________________________________________
> > seaside mailing list
> > [hidden email]
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside