[Seaside] 2.5 sushi store shopping cart & back button

Avi Bryant avi.bryant at gmail.com
Tue Nov 15 06:31:47 CET 2005

On Nov 14, 2005, at 9:28 PM, Nevin Pratt wrote:
> Avi,
> Have you thought about having the shopping cart one of the  
> 'getFields' fields of the HttpRequest?  Then, regardless of the  
> Seaside session expiry settings, the shopping cart would not expire  
> until the HttpRequest expired.  I think the result would be that  
> the shopping cart would be a bit more persistant than even the  
> Seaside sessions are, for the simple reason that the Seaside  
> sessions are somewhat decoupled from the HttpRequests right now.
> I've even wondered about keeping shopping carts permanent for each  
> connecting IP.  That would make them even more persistent and  
> permanent than having the shopping cart tied to cookies, and  
> without the intrusion that cookies has.  The problem with that  
> scheme, though, is that many different computers can masquerade  
> behind a single firewalled IP.
> I'm wondering about a way to have a shopping cart persist and be  
> permanent beyond Seaside sessions, and yet still be user-specific.   
> Something that would allow a user to, say, come back the next day  
> and still see their shopping cart items, but without using cookies.
> I know that the 'getFields' idea of the HttpRequest that I mention  
> above would not provide that level of persistence, but at least it  
> would be more persistent than the Seaside sessions.
> Any ideas?

Why not set a cookie for a shopping cart id?


More information about the Seaside mailing list