If your task is not interactive (i.e. there is no user waiting for the results), you can also use the maxlag paramter. [1]
This ensures that your task won't run when the load on the servers is high. Petr Onderka [[User:Svick]] [1]: http://www.mediawiki.org/wiki/Manual:Maxlag_parameter On Mon, Jan 23, 2012 at 06:35, Roan Kattouw <roan.katt...@gmail.com> wrote: > On Sun, Jan 22, 2012 at 10:51 PM, Fred Zimmerman <w...@nimblebooks.com> wrote: >> Is there any limit on frequency of requests to API? > There is no hard and fast limit on read requests, but we ask that you > be considerate and try not to take the site down. We also reserve the > right to unceremoniously block you if you do endanger the stability of > the site :) > > If you make your requests in series rather than in parallel (i.e. wait > for the first request to finish before sending the second request, > such that you're never making more than one request at the same time), > you should definitely be fine. You should also try to combine things > into one request where you can. > > Roan > > _______________________________________________ > Mediawiki-api mailing list > Mediawiki-api@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/mediawiki-api _______________________________________________ Mediawiki-api mailing list Mediawiki-api@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api
