umgeher/cowboy
0
Fork 0
mirror of https://github.com/ninenines/cowboy.git synced 2025-07-14 20:30:23 +00:00
Code Issues Wiki Activity
Small, fast, modern HTTP server for Erlang/OTP.
811 commits 6 branches 54 tags 12 MiB
Find a file
Loïc Hoguin ce1d8862c0 Replace init_stream/5 with stream_body/2 
This allows us to change the max chunk length on a per chunk basis
instead of for the whole stream. It's also much easier to use this
way even if we don't want to change the chunk size.
2013-04-02 19:40:38 +02:00
doc Add a simple README in the doc folder for guidance 2013-03-02 20:16:06 +01:00
examples Update Ranch to 0.6.2 2013-03-06 20:19:15 +01:00
guide Replace init_stream/5 with stream_body/2 2013-04-02 19:40:38 +02:00
src Replace init_stream/5 with stream_body/2 2013-04-02 19:40:38 +02:00
test Check the length before reading the body in body/1 and body_qs/1 2013-03-06 08:50:45 -05:00
.gitignore Add .cowboy.plt to the gitignore 2012-04-29 01:20:05 +02:00
AUTHORS Update AUTHORS 2013-03-09 14:45:15 +01:00
CHANGELOG.md Update CHANGELOG 2013-03-09 15:09:21 +01:00
CONTRIBUTING.md Add more details on how to report bugs and vulnerabilities 2013-02-27 18:25:45 +01:00
LICENSE Update version to 0.6.0 2012-05-23 14:53:48 +02:00
Makefile Update Ranch to 0.6.2 2013-03-06 20:19:15 +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.2 2013-03-06 20:19:15 +01:00
ROADMAP.md Add a REST point on the roadmap 2013-02-11 09:37:55 +01:00

README.md

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