From 647e95aed157edd58c86acdd774048593eb9d039 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Tue, 22 Jan 2013 02:34:18 +0100 Subject: 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. --- guide/loop_handlers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'guide/loop_handlers.md') diff --git a/guide/loop_handlers.md b/guide/loop_handlers.md index 64cf80a..c3d1891 100644 --- a/guide/loop_handlers.md +++ b/guide/loop_handlers.md @@ -31,7 +31,7 @@ practice is known as server-sent events. Loop handlers essentially wait for one or more Erlang messages and feed these messages to the `info/3` callback. It also features -the `init/3` and `terminate/2` callbacks which work the same as +the `init/3` and `terminate/3` callbacks which work the same as for plain HTTP handlers. The following handler waits for a message `{reply, Body}` before @@ -46,7 +46,7 @@ this message. -export([init/3]). -export([info/3]). --export([terminate/2]). +-export([terminate/3]). init({tcp, http}, Req, Opts) -> {loop, Req, undefined_state, 60000, hibernate}. @@ -57,6 +57,6 @@ info({reply, Body}, Req, State) -> info(Message, Req, State) -> {loop, Req, State, hibernate}. -terminate(Req, State) -> +terminate(Reason, Req, State) -> ok. ``` -- cgit v1.2.3