From: Eric Wong <normalperson@yhbt.net>
To: ruby.io.splice@librelist.org
Subject: removing MRI 1.8 support
Date: Thu, 12 May 2011 17:33:50 -0700 [thread overview]
Message-ID: <20110513003350.GA29438@dcvr.yhbt.net> (raw)
In-Reply-To: <20110513003350.GA29438@dcvr.yhbt.net>
Anybody really care for it?
I think it's too painful to support completely due to the way
SPLICE_F_NONBLOCK is handled for pipes and how the file O_NONBLOCK flag
of the non-pipe is relied on.
splice() ignores O_NONBLOCK on the pipe, instead relying on
SPLICE_F_NONBLOCK being passed to it. However, SPLICE_F_NONBLOCK
only affects pipes, so if you splice a pipe to a socket, you need
O_NONBLOCK on the socket.
Since MRI 1.8 uses non-blocking I/O and select() to schedule
threads, this is painful to deal with for users that may want
to see :EAGAIN or Errno::EAGAIN in some cases and not others.
Hopefully the above explaination is halfway coherent, I really
don't care enough about MRI 1.8 to do a better explanation :<
It may incidentally work in some/most cases, but 1.8 really isn't
worth my effort to maintain...
--
Eric Wong
next parent reply other threads:[~2011-05-13 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 0:33 Eric Wong [this message]
2011-05-13 8:06 ` removing MRI 1.8 support Iñaki Baz Castillo
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://yhbt.net/ruby_io_splice/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110513003350.GA29438@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=ruby.io.splice@librelist.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/ruby_io_splice.git/
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).