0
Fork 0
mirror of https://github.com/ninenines/cowboy.git synced 2025-07-14 20:30:23 +00:00
Small, fast, modern HTTP server for Erlang/OTP.
Find a file
Loïc Hoguin 40b8d0befc Better handle socket closing with loop handlers
We now read from the socket to be able to detect errors or TCP close
events, and buffer the data if any. Once the data receive goes over
a certain limit, which defaults to 5000 bytes, we simply close the
connection with an {error, overflow} reason.
2013-02-11 09:03:13 +01:00
doc Update version to 0.6.0 2012-05-23 14:53:48 +02:00
examples Add an example with custom middleware 2013-02-09 13:54:08 -06:00
guide Small routing guide fix 2013-01-31 00:41:14 +04:00
src Better handle socket closing with loop handlers 2013-02-11 09:03:13 +01:00
test Better handle socket closing with loop handlers 2013-02-11 09:03:13 +01:00
.gitignore Add .cowboy.plt to the gitignore 2012-04-29 01:20:05 +02:00
AUTHORS Update AUTHORS file 2012-08-09 10:02:18 +02:00
CHANGELOG.md Small Markdown fixes to better follow the specs 2012-12-07 16:19:08 +01:00
CONTRIBUTING.md Add note about 80 columns max to CONTRIBUTING file 2013-02-06 22:28:44 +01:00
LICENSE Update version to 0.6.0 2012-05-23 14:53:48 +02:00
Makefile Makefile: separate deps compilation from app compilation 2013-02-06 18:29:20 +01:00
README.md Salvage the README and move parts into the guide 2013-01-03 16:01:49 +01:00
rebar.config Update Ranch to 0.6.1 2013-01-29 01:20:16 +01:00
ROADMAP.md Update roadmap 2013-01-29 01:19:49 +01:00

Cowboy

Cowboy is a small, fast and modular HTTP server written in Erlang.

Goals

Cowboy aims to provide a complete HTTP stack in a small code base. It is optimized for low latency and low memory usage, in parts because it uses binary strings.

Cowboy provides routing capabilities, selectively dispatching requests to handlers written in Erlang.

Because it uses Ranch for managing connections, Cowboy can easily be embedded in any other application.

No parameterized module. No process dictionary. Clean Erlang code.

Getting Started

  • Read the guide
  • Look at the examples in the examples/ directory
  • Build API documentation with make docs; open doc/index.html

Support