I don't know much about this, but I think there is nothing special with web2py. The solution with background task looks good.
On the client side you can test finished results via ajax or just reload the page without javascript: <meta http-equiv="refresh" content="5"> The background task can check filesystem changes sometimes (from time import sleep), or can check filesystem changes with incron, or you can start the proccess from web2py controller (import subprocess or import asynproc; https://helloacm.com/execute-external-programs-the-python-ways/) and so on. So maybe - first page for upload; after successfull upload start the second proccess and redirect, - at second page look for results -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
