[Seaside] Usage of WASession>>sessionCookie

Philippe Marschall philippe.marschall at gmail.com
Mon May 7 08:20:16 UTC 2007

2007/5/7, Sophie Server <sophieb4 at gmx.de>:
> Hello everyone,
> I've just experienced some difficulties to implement a "Keep me logged in" mechanism.
> I want to use the "out - of - the box" - Session Cookie in order to have the session id of the current user stored in a cookie on the local machine, and the same session id stored into the database on my server.
> When starting a new session I thought of comparing the last session id of the user in my database and the "local" last session id read out if the cookie. If both match then the User could be logged in without password confirmation.
> The Problem with that built-in session cookie that it is set automatically with every new session, that means that the principle described above, does not work properly.
> To fix that I use a second cookie to store the old session Id - on demand (Keep me logged in is selected), but this was way is  highly redundant from my point of view:(.
> Finally, my actual Question: What is the actual use of that built-in session cookie?

Store the _s value (Seaside session id) in a cookie rather than an
URL. Nothing about "stay logged in", database sessions, userids,
persistent sessions whatsoever.

> Can I set it manually on demand?
What do you mean which that? In the middle of a session switch from _s
to a cookie or decide at the start of a session whether you want to
use a session cookie or not?

> Or am I on a completely wrong way?


> Thanks to all,
> Norman Holz
> --
> "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
> Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list