From: Juliusz Chroboczek <jch@irif.fr>
To: "Michael Ströder" <michael@stroeder.com>
Cc: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: Websocket close 1006 (abnormal closure): unexpected EOF
Date: Fri, 08 Jan 2021 15:58:47 +0100 [thread overview]
Message-ID: <87pn2f79w8.wl-jch@irif.fr> (raw)
In-Reply-To: <e189df9b-0599-9f62-c7a6-fd634b0e27db@stroeder.com>
>> 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, there are good
reasons to prefer simplicity of implementation and robustness to
performance. With nginx and IIS, a single buggy module will bring your
server down, while at least some configurations of Apache will happily
chug along after the PHP interpreter has crashed.
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.)
-- Juliusz
next prev parent reply other threads:[~2021-01-08 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 10:56 [Galene] " Jeroen van Veen
2021-01-05 14:42 ` [Galene] " Juliusz Chroboczek
2021-01-05 14:52 ` Toke Høiland-Jørgensen
2021-01-05 18:16 ` Jeroen van Veen
2021-01-05 18:44 ` Michael Ströder
2021-01-05 21:49 ` Toke Høiland-Jørgensen
2021-01-08 13:19 ` Juliusz Chroboczek
2021-01-08 14:24 ` Michael Ströder
2021-01-08 14:58 ` Juliusz Chroboczek [this message]
2021-01-08 16:03 ` Michael Ströder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn2f79w8.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
--cc=michael@stroeder.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox