[Seaside] [Newbie] Storing state in cookie instead of URL
stef at ummon.com
Sun Sep 7 17:50:55 UTC 2008
-----BEGIN PGP SIGNED MESSAGE-----
Philippe Marschall wrote:
> 2008/9/7 Stef Telford <stef at ummon.com>:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> Hello Everyone, So, I am playing around with Seaside.. generally
>> digging it and glad that I can do web development in my favourite
>> language (Ruby is nice, but, well, Smalltalk is nicer ;). I have
>> taken the first rudimentary steps, running Wakom, creating a
>> simple page and storing state.
>> However, when I was in the configure panel for my application, I
>> switched the 'Use Session Cookie' to 'true', yet I still get the
>> _k in my URL. I would have expected the value for _k to be stored
>> in the session cookie. If this doesn't do this, then I have two
>> 1) how do I get Seaside to use _k in cookies ?
> Not at all.
Ahhh.. judging from the reply, am I correct then in thinking that the
_s (session key) is then stored in the cookie after login/authn/authz
and because Smalltalk/Seaside has to grab objects from the
continuation, it has to know the _k value so that it can then find the
user objects, page objects, etc ?
In other words; To be able to get the objects (including the cookie
object), we need the _k outside so Smalltalk/Seaside can find it. If
that's the case, then the _k outside makes sense, and something I may
have to live with :)
Thanks for the quick reply btw.. pretty amazed - thank you :)
>> 2) what -does- 'use session cookie' do, if it doesn't put the
>> state (_k) into the cookie ?
> the _s value (he session key)
> Cheers Philippe _______________________________________________
> seaside mailing list seaside at lists.squeakfoundation.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the seaside