From: Eric Wong <normalperson@yhbt.net>
To: Ruby developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:69136] Re: [Ruby trunk - Feature #11139] [PATCH] socket: accept_nonblock supports "nonblock: false" kwarg
Date: Tue, 12 May 2015 00:58:38 +0000 [thread overview]
Message-ID: <20150512005838.GA13112@dcvr.yhbt.net> (raw)
In-Reply-To: <redmine.journal-52382.20150512002507.4f71e6a91ace5936@ruby-lang.org>
djberg96@gmail.com wrote:
> How about just :block ?
>
> a.accept(block: false)
> a.accept_nonblock(block: true)
I don't think that helps convey it affects the newly-accepted socket,
not the socket performing the accept. Perhaps :sock_nonblock is better,
at least it maps to SOCK_NONBLOCK in Linux.
next prev parent reply other threads:[~2015-05-12 0:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11139.20150512001411@ruby-lang.org>
2015-05-12 0:14 ` [ruby-core:69131] [Ruby trunk - Feature #11139] [Open] [PATCH] socket: accept_nonblock supports "nonblock: false" kwarg normalperson
2015-05-12 0:25 ` [ruby-core:69133] [Ruby trunk - Feature #11139] " djberg96
2015-05-12 0:58 ` Eric Wong [this message]
2015-06-14 10:09 ` [ruby-core:69576] [Ruby trunk - Feature #11139] [Feedback] " akr
2015-06-15 23:40 ` [ruby-core:69594] " Eric Wong
2015-06-16 1:53 ` [ruby-core:69598] [Ruby trunk - Feature #11139] " akr
2015-06-16 3:35 ` [ruby-core:69600] " akr
2015-06-22 19:36 ` [ruby-core:69703] " Eric Wong
2015-06-25 2:29 ` [ruby-core:69733] " akr
2015-07-02 1:30 ` [ruby-core:69835] [Ruby trunk - Feature #11139] [PATCH] socket: support accept `sock_nonblock: (true|false)' normalperson
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150512005838.GA13112@dcvr.yhbt.net \
--to=ruby-core@ruby-lang.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).