Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of suraj.kumar@inmobi.com
 designates 209.85.213.174 as permitted sender)
MIME-Version: 1.0
Date: Fri, 27 Jun 2014 15:19:30 +0530
Message-ID: 
 <CABadZm+cvVOaP+F8uPJaBjNTsKrwUC9kG2+SHfTYO1uykDovQA@mail.gmail.com>
Subject: Per-user rate-limiting of writes
From: Suraj Kumar <suraj.kumar@inmobi.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=20cf3042745ad3280a04fcce392e

--20cf3042745ad3280a04fcce392e
Content-Type: text/plain; charset=UTF-8

Hi,

We use CouchDB's _users DB extensively for authentication. We'd like to
rate-limit the number of writes to CouchDB per user. How can this be
achieved? One way is to make a web-server do the rate-limiting. But we're
really looking for rate limiting how many docs a given user can have in the
system beyond which writes should 'fail'. How can this be done? I can think
of ways to 'keep no more than N docs per user' but I'd ideally like to
inform the user via HTTP response then and there when write rate-limit
threshold has crossed.

Is this possible?

Thanks,

  -Suraj

-- 
An Onion is the Onion skin and the Onion under the skin until the Onion
Skin without any Onion underneath.

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

--20cf3042745ad3280a04fcce392e--