From: tomas@tuxteam.de
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: guile-user@gnu.org
Subject: Re: Fibers web server: use multiple server sockets
Date: Wed, 2 Nov 2022 20:57:38 +0100 [thread overview]
Message-ID: <Y2LLsi+RTRtUlH+y@tuxteam.de> (raw)
In-Reply-To: <87k04dtahl.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
On Wed, Nov 02, 2022 at 08:35:24PM +0100, Dr. Arne Babenhauserheide wrote:
>
> <tomas@tuxteam.de> writes:
> > As far as I understand Vivien, interfaces come and go during the
> > server's lifetime. I.e. it's not just a "boot" thing. This seems
> > like a valid use case.
> On some servers you might actually pull out an interface during runtime
> to hotswap a new one — for example because it signaled that it is short
> of failing.
Yes, but as Vivien explained his case, just the other side of the network
might go down. Or the dhcp server at the other side takes too long and we
don't want to block the boot. Or the sysadmin just does "ifdown eth0"
and somewhat later "ifup...". Or whatever.
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-11-02 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 18:15 Fibers web server: use multiple server sockets dsmich
2022-11-02 18:27 ` Vivien Kraus
2022-11-02 19:19 ` tomas
2022-11-02 19:35 ` Dr. Arne Babenhauserheide
2022-11-02 19:57 ` tomas [this message]
2022-11-02 23:04 ` Ricardo Wurmus
-- strict thread matches above, loose matches on Subject: below --
2022-11-02 16:37 Vivien Kraus
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y2LLsi+RTRtUlH+y@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).