I think for your use case, you may want to consider using Tactic instead of Web2py.
On Friday, April 4, 2014 12:58:54 PM UTC-7, Francisco Betancourt wrote: > > I must call it from my server, data from csv is processed, and this data > is sent to the web service. Also I was hopping that since it's our server > the one working on this, user can close their browser and come back hours > later to see the progress rather than needing to have their browsers open > for so much time. And that is another point for the scheluder. > > El viernes, 4 de abril de 2014 13:39:22 UTC-6, Leonel Câmara escribió: >> >> > Didn't knew you could do this. But sadly users preview the data >> uploaded before the process and require the information to be stored for >> archival purposes for a good amount of time (say years) so I do need the db. >> >> Well, unless they need to do some stuff with this data besides archiving >> somehow, you can just save the csv file they have just uploaded. >> >> Whoever is providing the webservice is retarded :) >> >> Is your server the one calling the webservice or the client? If it's the >> client there's not much of a point in even considering the scheduler and >> instead you may consider using webworkers. If it is the server you >> definitely should use the scheduler, you should also look and see if it's >> possible to cache the webservice responses. >> > -- 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.
