From 09adc1acb42ffe10a3a4991ea2368ab0784e5d66 Mon Sep 17 00:00:00 2001 From: JT Smith Date: Wed, 16 Mar 2011 00:16:38 -0500 Subject: [PATCH] rpc limits --- docs/Intro.pod | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Intro.pod b/docs/Intro.pod index 5cf626af..202dd94e 100644 --- a/docs/Intro.pod +++ b/docs/Intro.pod @@ -109,7 +109,7 @@ B If you get a JSON-RPC error, then the web server will also give you a 5 =head2 RPC Limit -You may only make a number of calls up to the RPC Limit in a given 24 hour period. The current limit is 5000. At the current limit you you can make about 3.5 calls per minute all day long. The counter resets roughly (give or take 60 minutes) at midnight GMT. Your RPC calls are counted across all clients you use and your own programs. +You may only make a number of calls up to the RPC Limit in a given 24 hour period. The current limit is 10,000. They are also rate limited to 75 calls per minute. The counter resets roughly (give or take 60 minutes) at midnight GMT. Your RPC calls are counted across all clients you use and your own programs. If you find yourself needing more RPC calls than the limit allows then you are likely making a lot of redundant requests. For example body.get_buildings() returns the entire list of buildings, and a time as to when their stats will change. So instead of calling every building on every planet every time your program looks something up, cache it until it changes. -- 2.51.2