> 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.
