cowboy.git - Small, fast, modern HTTP server for Erlang/OTP.

Age	Commit message (Collapse)	Author
2013-02-22	Fix to prevent loop handler awakening immediately after response sent	James Fish
	If a loop handler sent a response (e.g. cowboy_req:chunked_reply/2,/3) and then returns {loop, Req, HandlerState, hibernate} it would have a {cowboy_req, resp_sent} message in its message queue. This message would cause the process to immediately awaken, so it is flushed before hibernation.
2013-02-21	Added warn compile options. Fixed compile warnings.	Egobrain

2013-02-17	Fix {suspend, ...} specs to use atom() for function name	James Fish

2013-02-15	Make sure socket is passive once we've done with loop handler	Andrew Majorov
	It is sometimes important to make a socket passive as it was initially and as it is expected to be by cowboy_protocol, right after we've done with loop handling.
2013-02-11	Better handle socket closing with loop handlers	Loïc Hoguin
	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-01-29	Fix {cowboy_req, resp_sent} potentially leaking in loop handlers	Loïc Hoguin

2013-01-22	Replace terminate/2 with terminate/3, adding a Reason	Loïc Hoguin
	This should have been done a long time ago, back when I initially added Websocket support. This is the first part of two in improving loop handler support with regards to socket closure. Reason may include: {normal, shutdown} for the most normal shutdown, {normal, timeout} for a loop handler timeout shutdown, or {error, _} if an error occured.
2013-01-03	Add middleware support	Loïc Hoguin
	Middlewares allow customizing the request processing. All existing Cowboy project are incompatible with this commit. You need to change `{dispatch, Dispatch}` in the protocol options to `{env, [{dispatch, Dispatch}]}` to fix your code.