[Seaside] sharing sessions through links..
Boris Popov
boris at deepcovelabs.com
Tue Oct 28 21:07:01 UTC 2008
Because the test is such that it feeds browser a cookie and monitors if it receives it back, which would indicate browser supports them.
Cheers!
-Boris (via BlackBerry)
----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
Sent: Tue Oct 28 14:05:15 2008
Subject: Re: [Seaside] sharing sessions through links..
Nevin Pratt wrote:
> Boris Popov wrote:
>> Nevin,
>>
>> It already does, see senders of #checkCookiesField for more detail,
>>
>> Cheers,
>>
>> -Boris
>>
>>
> Ah, OK! A sender of #checkCookiesField is WASession>>performRequest:,
> and the browser check seems to be done as follows:
>
> aRequest fields includesKey: self checkCookiesField
>
> Thanks!
>
> Nevin
WASession>>useSessionCookie
^ cookiesEnabled
and: [self application useSessionCookie]
So, apparantly 'cookiesEnabled' is exactly what I want, and I don't have
to do the browser check code I mention above.
However, cookiesEnabled is set to 'false' under the following conditions:
((aRequest fields includesKey: self checkCookiesField)
and: [aRequest cookies isEmpty])
ifTrue: [cookiesEnabled := false].
My question is: why do we care if 'aRequest cookies isEmpty'? Why
should that have anything to do with whether or not the browser accepts
cookies?
Nevin
_______________________________________________
seaside mailing list
seaside at lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20081028/85b092f4/attachment.htm
More information about the seaside
mailing list