aboutsummaryrefslogtreecommitdiffstats
path: root/test/websocket_handler_init_shutdown.erl
diff options
context:
space:
mode:
authorJames Fish <[email protected]>2013-02-17 00:17:43 +0000
committerJames Fish <[email protected]>2013-02-22 18:36:13 +0000
commitb61f535134adb35df35c16b6eebe51b3d14aaf48 (patch)
tree1d7343813fb1128c29969caa75640bcc18d76c4e /test/websocket_handler_init_shutdown.erl
parent6884a4949b5235eb809996228406c659a349fc60 (diff)
downloadcowboy-b61f535134adb35df35c16b6eebe51b3d14aaf48.tar.gz
cowboy-b61f535134adb35df35c16b6eebe51b3d14aaf48.tar.bz2
cowboy-b61f535134adb35df35c16b6eebe51b3d14aaf48.zip
Fix to prevent loop handler awakening immediately after response sent
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.
Diffstat (limited to 'test/websocket_handler_init_shutdown.erl')
0 files changed, 0 insertions, 0 deletions