cowboy/test/ws_SUITE_data/ws_timeout_hibernate.erl

%% Feel free to use, reuse and abuse the code in this file.

-module(ws_timeout_hibernate).
-behaviour(cowboy_websocket_handler).
-export([init/3]).
-export([websocket_init/3, websocket_handle/3,
	websocket_info/3, websocket_terminate/3]).

init(_Any, _Req, _Opts) ->
	{upgrade, protocol, cowboy_websocket}.

websocket_init(_TransportName, Req, _Opts) ->
	{ok, Req, undefined, 1000, hibernate}.

websocket_handle(_Frame, Req, State) ->
	{ok, Req, State, hibernate}.

websocket_info(_Info, Req, State) ->
	{ok, Req, State, hibernate}.

websocket_terminate(_Reason, _Req, _State) ->
	ok.
Add a test for websocket hibernate + timeout and fix this use case The issue was that we were calling erlang:hibernate before a receive .. after .. end call. Erlang hibernates the process before reaching the receive instruction and we therefore couldn't enter the after clause when hibernating. This is now fixed by using erlang:send_after instead and receiving that message instead of using an after clause. 2011-09-22 21:33:56 +02:00			`%% Feel free to use, reuse and abuse the code in this file.`

Reorganize the websocket test suite We now have the suite specific modules in the data folder. Compilation is performed by the Makefile instead of ct_run. 2013-04-22 15:55:22 +02:00			`-module(ws_timeout_hibernate).`
Update behaviours for R15B+ This effectively drops the R14B compatibility. The cowboy_req:req() type will be introduced in a future commit. It refers to the #http_req{} record. 2012-08-27 12:46:42 +02:00			`-behaviour(cowboy_websocket_handler).`
Replace terminate/2 with terminate/3, adding a Reason 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-22 02:34:18 +01:00			`-export([init/3]).`
Add a test for websocket hibernate + timeout and fix this use case The issue was that we were calling erlang:hibernate before a receive .. after .. end call. Erlang hibernates the process before reaching the receive instruction and we therefore couldn't enter the after clause when hibernating. This is now fixed by using erlang:send_after instead and receiving that message instead of using an after clause. 2011-09-22 21:33:56 +02:00			`-export([websocket_init/3, websocket_handle/3,`
			`websocket_info/3, websocket_terminate/3]).`

			`init(_Any, _Req, _Opts) ->`
Rename cowboy_http_websocket to cowboy_websocket 2012-08-27 14:00:28 +02:00			`{upgrade, protocol, cowboy_websocket}.`
Add a test for websocket hibernate + timeout and fix this use case The issue was that we were calling erlang:hibernate before a receive .. after .. end call. Erlang hibernates the process before reaching the receive instruction and we therefore couldn't enter the after clause when hibernating. This is now fixed by using erlang:send_after instead and receiving that message instead of using an after clause. 2011-09-22 21:33:56 +02:00
			`websocket_init(_TransportName, Req, _Opts) ->`
			`{ok, Req, undefined, 1000, hibernate}.`

			`websocket_handle(_Frame, Req, State) ->`
			`{ok, Req, State, hibernate}.`

			`websocket_info(_Info, Req, State) ->`
			`{ok, Req, State, hibernate}.`

			`websocket_terminate(_Reason, _Req, _State) ->`
			`ok.`