[Seaside] Issue with #checkForCookies

Avi Bryant avi.bryant at gmail.com
Wed Aug 31 06:22:52 CEST 2005

On Aug 30, 2005, at 9:52 PM, Julian Fitzell wrote:
> I don't see any reason why you couldn't just tack a cookie onto a  
> response
> with #cookieAt:Put: or #addCookie: if you didn't need it until  
> later.  There's
> a space on WARenderingContext for storing the response (and in fact
> WAHtmlRenderer>>response returns it) but it doesn't seem to be set in
> WARenderLoop>>render and nothing seems to use it.
> Avi, is there some reason we're not setting the response on the  
> context
> anymore or is it just an omission?.

Looks like an omission.  The response has already been created by the  
time we do the render pass, there's no reason not to give things  
access to it.

The main advantage of the redirect approach to using cookies is that  
the API can be used from callbacks rather than from render code,  
which seems like a more likely place to know you want to set a cookie.


More information about the Seaside mailing list