I believe this has been resolved here: http://stackoverflow.com/a/35613922/440323
Anthony On Friday, February 26, 2016 at 10:03:30 AM UTC-5, NeoToren wrote: > > In order for a progress bar using cache.ram, and an ajax call to work > properly, there is a need to clean (or just unlock?) sessions. > If the app doesn't use session variables to pass to other controllers then > session.forget(response) is sufficient. > > If on the other hand, the app needs session variables (as my app does > indeed) - then session.forget doesn't do much good since it brakes the > session variables chain of transmission to other controllers. > > As per Anthony suggestion in another post (Progress bar and sessions): > > I tried first using the cookies (with maximum zlib compression - level 9) > . > Still it's not enough for my needs ... I need more than 10k per session to > be passed to other controllers, and as mentioned in the book - keeping > sessions in cookies is not a good solution if the session are expected to > be large (more than 4k/cookie I assume). > > So I am trying session.connect with a MySQL db. > I can see the table *web2py_session_AppName* being populated and I > understand the *session_data* column is pickled with cPickle. > However...It looks the data in this column, *session_data* is encrypted, > not just pickled. > > *How do I unpickle the information in session_data column from a MySQL > table ?* > I tried using cPickle.loads...with the data as is, with the data as a > string...but it still throws a "bad pickle error" > > Thanks > -- 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.