mirror of
https://github.com/ninenines/cowboy.git
synced 2025-07-15 12:40:25 +00:00
Rename 'shutdown' close reason and tuples to 'stop'
The 'shutdown' atom has a specific meaning inside OTP. We are instead going to use 'stop' which is pretty much the equivalent of what we actually do. 'shutdown' is now reserved for future special processes implementation.
This commit is contained in:
parent
903f6f4c7d
commit
8cbd8c1882
10 changed files with 46 additions and 47 deletions
|
@ -61,7 +61,7 @@ message otherwise.
|
|||
``` erlang
|
||||
info({reply, Body}, Req, State) ->
|
||||
Req2 = cowboy_req:reply(200, [], Body, Req),
|
||||
{shutdown, Req2, State};
|
||||
{stop, Req2, State};
|
||||
info(_Msg, Req, State) ->
|
||||
{ok, Req, State, hibernate}.
|
||||
```
|
||||
|
@ -76,7 +76,7 @@ return a tuple indicating if more messages are to be expected.
|
|||
The callback may also choose to do nothing at all and just
|
||||
skip the message received.
|
||||
|
||||
If a reply is sent, then the `shutdown` tuple should be returned.
|
||||
If a reply is sent, then the `stop` tuple should be returned.
|
||||
This will instruct Cowboy to end the request.
|
||||
|
||||
Otherwise an `ok` tuple should be returned.
|
||||
|
@ -99,7 +99,7 @@ init(Req, Opts) ->
|
|||
{cowboy_loop, Req2, Opts}.
|
||||
|
||||
info(eof, Req, State) ->
|
||||
{shutdown, Req, State};
|
||||
{stop, Req, State};
|
||||
info({chunk, Chunk}, Req, State) ->
|
||||
cowboy_req:chunk(Chunk, Req),
|
||||
{ok, Req, State};
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue