>> The problem comes when the user/browser gives up and cancels the request, >> and immediately resubmits (or simply gets impatient and does a reload). In >> my case, things would get so tangled that I'd have to restart web2py.
I think the proper way to deal with this is having a queue of tasks with some type of scheduling. There are many use-cases when a webapp is merely a web-based interface to compute-intensive applications running on the server(s). As such, web2py might want to have built-in support for these types of uses.
