aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKlaus Trainer <[email protected]>2013-11-26 21:13:43 +0100
committerKlaus Trainer <[email protected]>2013-11-26 21:13:43 +0100
commitd139b6f11019da67c609df5b5688d701b35e62a9 (patch)
tree0fa418c7b7274a642f16042d23350e6c12027b57
parentdf818625545d565b8b76fbc445063a4822114b93 (diff)
downloadcowboy-d139b6f11019da67c609df5b5688d701b35e62a9.tar.gz
cowboy-d139b6f11019da67c609df5b5688d701b35e62a9.tar.bz2
cowboy-d139b6f11019da67c609df5b5688d701b35e62a9.zip
manual: Add note about cowlib
-rw-r--r--manual/cowboy_app.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/manual/cowboy_app.md b/manual/cowboy_app.md
index 9fe316d..2a086de 100644
--- a/manual/cowboy_app.md
+++ b/manual/cowboy_app.md
@@ -7,8 +7,9 @@ Dependencies
------------
The `cowboy` application uses the Erlang applications `ranch`
-for listening and accepting TCP connections, and `crypto`
-for establishing Websocket connections. These dependencies must
+for listening and accepting TCP connections, `crypto` for
+establishing Websocket connections, and `cowlib` for parsing and
+building messages for Web protocols. These dependencies must
be loaded for the `cowboy` application to work. In an embedded
environment this means that they need to be started with the
`application:start/{1,2}` function before the `cowboy`