From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] accept4: add support for SOCK_NONBLOCK when using accept()
Date: Thu, 30 Jul 2020 01:00:06 -0700 [thread overview]
Message-ID: <CA+XASoVyA9fBR7hj83FdZGkj=TrT3ZG3mkqwggVG1nrR7_p34w@mail.gmail.com> (raw)
In-Reply-To: <CA+XASoVd05HcpU35R60e0aWTG=r+AyWcVShFJKo5HFwcOB-Cdg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
Fibers work on macOS is being done here.
https://github.com/wingo/fibers/pull/42
This is now working with both web servers.
On Wed, Jul 29, 2020 at 5:06 PM Aleix Conchillo Flaqué <aconchillo@gmail.com>
wrote:
> SOCK_NONBLOCK was not implemented when accept4() is not available (e.g.
> macOS).
>
> I'm currently testing all this with the two new web server implementations
> provided with Fibers.
>
> Aleix
>
[-- Attachment #2: Type: text/html, Size: 1453 bytes --]
prev parent reply other threads:[~2020-07-30 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 0:06 [PATCH] accept4: add support for SOCK_NONBLOCK when using accept() Aleix Conchillo Flaqué
2020-07-30 8:00 ` Aleix Conchillo Flaqué [this message]
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='CA+XASoVyA9fBR7hj83FdZGkj=TrT3ZG3mkqwggVG1nrR7_p34w@mail.gmail.com' \
--to=aconchillo@gmail.com \
--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).