From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-devel@gnu.org
Subject: Re: [PATCH v3] Define SO_RCVTIMEO and SO_SNDTIMEO.
Date: Wed, 12 Oct 2022 22:28:22 +0200 [thread overview]
Message-ID: <87ilkovlax.fsf@gnu.org> (raw)
In-Reply-To: 20220918141734.17544-1-mail@cbaines.net
Hi,
Christopher Baines <mail@cbaines.net> skribis:
> These are important for reliable networking, since they prevent network
> operations from hanging indefinitely.
>
> * libguile/socket.c (scm_init_socket): Define SO_RCVTIMEO and
> SO_SNDTIMEO.
> (scm_getsockopt, scm_setsockopt): Include SO_RCVTIMEO and SO_SNDTIMEO in
> docstring and handle them.
> * doc/ref/posix.texi (Network Sockets and Communication): Document them.
Applied, thanks!
Ludo’.
next prev parent reply other threads:[~2022-10-12 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 8:05 [PATCH] Define SO_RCVTIMEO and SO_SNDTIMEO Christopher Baines
2022-09-17 9:40 ` Maxime Devos
2022-09-18 14:11 ` Christopher Baines
2022-09-18 13:56 ` [PATCH v2] " Christopher Baines
2022-09-18 14:17 ` [PATCH v3] " Christopher Baines
2022-10-12 20:28 ` Ludovic Courtès [this message]
2022-10-13 10:28 ` Christopher Baines
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=87ilkovlax.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).