From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113]) by mail.toke.dk (Postfix) with ESMTPS id 9C6DB7C77A9 for ; Fri, 8 Jan 2021 17:03:41 +0100 (CET) Authentication-Results: mail.toke.dk; dkim=pass (1536-bit key) header.d=stroeder.com header.i=@stroeder.com header.b=jQ2qTkB3 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=stroeder.com; s=stroeder-com-20201114; t=1610121819; bh=avVB3XR1mekLsnFEz2Yuq9A58Mn9PAWzLVjkiQblM28=; h=Subject:To:References:From:Date:In-Reply-To:From; b=jQ2qTkB3GUYYuwE5hBSRFZiUSUnESlIMuQhLU5BkdkWI0n5eOA9pC4fCq1UelRxuO SAGjhQycSoAXWQ27TjyBdmi7nVV1gqZevGaSWaiJIgLY5vaG7zQXBjVysvYpJ6XTsy b5sEZznJ6z5Nf7TWFhZlHekX8UKf7BqNHBv8zcX7zxwX21gdrwFBrLrP8AR7807bHm I8834bqbth2Q7GYM0iloSz7LtAofG4wJI5Ay8eMp2l2utkADkoncxgxY1wf To: "galene@lists.galene.org" References: <0-dxBS5LC_odE5dSkuOGwoOb2FmQ7PYcbBgSGpmtz2R1ek9xklqHKQ6UCO11J1JvU5np1csOcujLTfM3ZU_48ub3yZ1EQRcYuTbarD6EkN4=@protonmail.com> <87turv78ed.wl-jch@irif.fr> <87v9cba11z.fsf@toke.dk> <59143aab-df95-92d8-db78-3129c2e02fb4@stroeder.com> <87wnwn7eid.wl-jch@irif.fr> <87pn2f79w8.wl-jch@irif.fr> From: =?UTF-8?Q?Michael_Str=c3=b6der?= Message-ID: <02ca2ccd-779b-a56d-cb96-7b5c5c14c38f@stroeder.com> Date: Fri, 8 Jan 2021 17:03:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <87pn2f79w8.wl-jch@irif.fr> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Message-ID-Hash: W4CO6K2XK5EGF4ORLRB6HR7KU4KHXVL7 X-Message-ID-Hash: W4CO6K2XK5EGF4ORLRB6HR7KU4KHXVL7 X-MailFrom: michael@stroeder.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.3.2 Precedence: list Subject: [Galene] Re: Websocket close 1006 (abnormal closure): unexpected EOF List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: On 1/8/21 3:58 PM, Juliusz Chroboczek wrote: >>> The tradition to use small timeouts comes from Apache, which used to use >>> up a whole process for every connection, even when idle. > >> This should not be an issue with Apache's MPM event model anymore. Right? > > I'm not sure how Apache's reverse proxy module is implemented. Probably > well, but I haven't checked. > > (I didn't mean my previous message as a dig at Apache, I did not read any negative attitude in your previous message. > I did mean it as a dig at people who use the same timeouts for HTTP and > WebSockets. This practice has a real cost in terms of mobile battery usage.) Noted. These hints are highly appreciated. Ciao, Michael.