From c9d23b9932dc0a9df99d96b6ff2f309a684f8ea3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Wed, 8 May 2019 18:02:15 +0200 Subject: Remove a paragraph about the old socket option --- doc/src/guide/listeners.asciidoc | 7 ------- 1 file changed, 7 deletions(-) (limited to 'doc') diff --git a/doc/src/guide/listeners.asciidoc b/doc/src/guide/listeners.asciidoc index e7ecfec..24fb455 100644 --- a/doc/src/guide/listeners.asciidoc +++ b/doc/src/guide/listeners.asciidoc @@ -172,13 +172,6 @@ The custom `listen/1` function must ensure that the listener process of the socket it returns. Failing to do so will result in stop/start and suspend/resume not working properly for that listener. -While it might be tempting to pass in an existing socket to your -custom transport by way of the transport options, thereby mimicking -a deprecated ranch behavior, this is considered dangerous and was removed -for that very reason. In general, it should be ensured that the socket -to be returned from a custom `listen/1` function really is a listening -socket and that it is operational. - === Limiting the number of concurrent connections The `max_connections` transport option allows you to limit the number -- cgit v1.2.3