Thanks Niphlod. With session.forget on both controllers and while progress is working, getprog returns a response right away with the initial value, not the current one.
It seems that cache.ram acts like the session object, it doesnt change until the initial request (progress) finishes. Which is something that doesnt happen on localhost only on production. Looks like there are some blocking operations on this case. Any suggestion? is there any simpler way to implement a progress bar without having to smash the db if posible? -- 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.
