On Tuesday, February 24, 2015 at 1:13:59 PM UTC-8, Niphlod wrote: > > [...] >
> The thing is, usually webservers put a hard timeout on the time it takes > to generate a result, so if your "rest api calls" are taking more than > -e.g.- 60 seconds, the right thing to do is to avoid using the webserver > and let another "thing" to do it, and store the results somewhere your page > can fetch them, without incurring in the timeout > > >> What is the best approach to fire all of these calls simultaneously >> instead of sequentially? >> > > ajax would be my first and obvious choice. > > I have a small internal app that polls several machines to display status information. I did the message handling in-line for a first cut, but I'm thinking about moving that part into the scheduler, maybe using a temporary table for the results although I expect a temp file would also work, while having the original page just be an ajax load of the-results-so-far that gets updated by a timer until enough time has passed. Since the enhancement is a background task, it may take me a while to get started, even though the coding looks small. /dps -- 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.
