From 047ea9eedbb84573cc68ccb1320fdb32234ccc39 Mon Sep 17 00:00:00 2001
From: Yorhel <git@yorhel.nl>
Date: Sun, 8 Nov 2009 17:17:19 +0100
Subject: API: Changed 30 cmds/min. throttle to 100 cmds/10min.

More bursting, but overall less commands... sounds more fair to me, for
both server resources and API usage.
---
 data/docs/11 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'data/docs')

diff --git a/data/docs/11 b/data/docs/11
index ba27b2bb..eb7c3aae 100644
--- a/data/docs/11
+++ b/data/docs/11
@@ -53,7 +53,7 @@ server resources and prevent abuse of this service.</p>
  <li>5 connections per IP. All connections that are opened after reaching this limit will be immediately closed.</li>
  <li>3 connections per user. The login command will reply with a 'sesslimit' error when reaching this limit.</li>
  <li>Each command currently returns at most 10 results. <i>TODO: make configurable?</i></li>
- <li>30 commands per minute per user. Server will reply with a 'throttled' error (type="cmd") when reaching this limit.</li>
+ <li>100 commands per 10 minutes per user. Server will reply with a 'throttled' error (type="cmd") when reaching this limit.</li>
  <li>
   1 second of SQL time per minute per user. SQL time is the total time taken to
   run the database queries for each command.  This depends on both the command
-- 
cgit v1.2.3