aboutsummaryrefslogtreecommitdiffstats
path: root/doc/src/guide
diff options
context:
space:
mode:
authorLoïc Hoguin <[email protected]>2018-11-14 15:57:38 +0100
committerLoïc Hoguin <[email protected]>2018-11-14 18:04:31 +0100
commitc65e3ff20e0cf64c574d98550c2a88527dde49ce (patch)
tree83b81f47c7f2c62d04d034270dc9e8480864317f /doc/src/guide
parent637a9b39249cf573b82d2493b7cedcf324b8537c (diff)
downloadcowboy-c65e3ff20e0cf64c574d98550c2a88527dde49ce.tar.gz
cowboy-c65e3ff20e0cf64c574d98550c2a88527dde49ce.tar.bz2
cowboy-c65e3ff20e0cf64c574d98550c2a88527dde49ce.zip
Add a use case to loop handlers
Diffstat (limited to 'doc/src/guide')
-rw-r--r--doc/src/guide/loop_handlers.asciidoc3
1 files changed, 2 insertions, 1 deletions
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