From 8c9ad7bf078871295e391f416bfcb10c9156a35f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= <essen@ninenines.eu>
Date: Sun, 4 Nov 2018 11:51:35 +0100
Subject: Add the rate_limited/2 REST callback

---
 doc/src/guide/resource_design.asciidoc | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'doc/src/guide/resource_design.asciidoc')

diff --git a/doc/src/guide/resource_design.asciidoc b/doc/src/guide/resource_design.asciidoc
index fa0c612..4ea0390 100644
--- a/doc/src/guide/resource_design.asciidoc
+++ b/doc/src/guide/resource_design.asciidoc
@@ -122,6 +122,9 @@ Can access to a resource be forbidden regardless of access
 being authorized? A simple example of that is censorship
 of a resource. Implement the `forbidden` callback.
 
+Can access be rate-limited for authenticated users? Use the
+`rate_limited` callback.
+
 Are there any constraints on the length of the resource URI?
 For example, the URI may be used as a key in storage and may
 have a limit in length. Implement `uri_too_long`.
-- 
cgit v1.2.3

