I don't know that i'm having that same issue, i'm not actually using a 
database behind this app. i'm basically just sending some data to a python 
function and re-calling this function over and over to visualize the 
computing.  I'm guessing that the issue is based on the fact that the 
production server is on a farm as that's the only difference between my 
working code and the code that isn't working

On Thursday, October 2, 2014 7:27:41 PM UTC-4, Leonel Câmara wrote:
>
> If you're indeed having the same problem as that stackoverflow question, 
> what you can do is you can store the sessions in the database, or you can 
> store them in the client's cookies (this has some security implications).
>
> You have detailed explanations on how to do this with web2py here:
>
> http://web2py.com/books/default/chapter/29/04/the-core?search=session#session
>
>

-- 
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.

Reply via email to