Re: [web2py] Re: Long-running controllers

[Anthony]

On Wednesday, January 19, 2011 1:35:09 AM UTC-5, Jonathan Lundell wrote: 
>
> Actually, there's a bug in the documentation (or else in Session). You have 
> to say: 
>
>     session.forget(response) 
>
> or else the session doesn't get unlocked
>
There are at least four occurrences of session.forget() in the book, and one 
in the 'call' action in the default.py controller of the 'welcome' app. 
Should all of those be replaced with session.forget(response)? Is there any 
reason to use session.forget() with the default response=None (which sets 
session._forget=True but does not unlock the session file)? If not, maybe 
the default behavior of session.forget() itself should be changed.