On Tue, Dec 21, 2004 at 09:32:54AM -0500, Geoffrey Talvola wrote:
> [EMAIL PROTECTED] wrote:
> > My site has a site-wide cookie for some user preferences, and
> > some pages use sessions to store as much as 10 Meg of data
> > on the server with session paths in case users have their
> > cookies disabled. With the new CVS version of Application.py
> > cookies and session paths are now mutually exclusive, and
> > this type of site design will not work. Would it be
> > possible for this to optionally be handled as an unnecessary
> > path session rather than doing so in all cases?
>
> I would be happy to make changes, but I'm curious why the current code in
> CVS won't work for you. The code is supposed to only use session IDs
> embedded in the path when cookies are disabled, which seemed reasonable to
> me at the time.
If the user allows cookies, I hold some site-wide preferences in a site
cookie (cookie path '/'). Whether cookies are are disabled or not,
I hold large amounts of data in a session variable. The current code
sees that cookies are not disabled, i.e. my site-wide preferences
cookie, and so handles the session paths as unnecessary and
prevents code access to the session data due to the session-path-less
redirect.
Since the amount of data is large and the user may not allow cookies,
session paths allow me to store the data on the server and not pass it
back and forth. I would still like the users to set and keep some
preferences on a longer-term basis which means a cookie.
James Phillips
http://zunzun.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss
