I love the new(?) capability of storing the session information in a browser cookie. Mainly because I'm lazy and don't want the responsibility of determining when to throw out sessions and manage them on my end.
I added this to my app: session.connect(request, response, cookie_key="mylittleponytasteslikechicken") Everything works.... mostly. I have seen some corner cases not working correctly, such as a form that doesn't have a "formkey" stored in the session when I am impersonating a user. Paging thru the session variable in this last case I noticed there's a LOT of stuff in the session, and I wonder if the size of the cookie might be causing its truncation? What are the practical limits of using browser cookies to hold session data, and are there workaround for large-ish sessions? Joe -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
