From c65e3ff20e0cf64c574d98550c2a88527dde49ce Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= <essen@ninenines.eu>
Date: Wed, 14 Nov 2018 15:57:38 +0100
Subject: Add a use case to loop handlers

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

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

diff --git a/doc/src/guide/loop_handlers.asciidoc b/doc/src/guide/loop_handlers.asciidoc
index 9e29b11..e574854 100644
--- a/doc/src/guide/loop_handlers.asciidoc
+++ b/doc/src/guide/loop_handlers.asciidoc
@@ -14,7 +14,8 @@ most known example of such practice is known as long polling.
 Loop handlers can also be used for requests where a response is
 partially available and you need to stream the response body
 while the connection is open. The most known example of such
-practice is server-sent events.
+practice is server-sent events, but it also applies to any
+response that takes a long time to send.
 
 While the same can be accomplished using plain HTTP handlers,
 it is recommended to use loop handlers because they are well-tested
-- 
cgit v1.2.3

