kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / Atom feed
From: Eric Wong <e@80x24.org>
To: kgio-public@bogomips.org, ruby-talk@ruby-lang.org
Subject: [ANN] kgio 2.11.0 - legacy I/O for legacy Ruby + Unix
Date: Fri, 16 Dec 2016 23:18:37 +0000
Message-ID: <20161216-kgio-2.11.0-released@fail> (raw)

kgio provides non-blocking I/O methods for Ruby without raising
exceptions on EAGAIN and EINPROGRESS.  It is intended for use with the
unicorn Rack server, but may be used by other applications (that run on
Unix-like platforms).

Note: I do not recommend using kgio for future applications, Ruby 2.x
has a lot of the functionality of kgio and Ruby 2.3 has even more.
Keep an eye on the NEWS file for Ruby 2.3+ releases.
However, I'll continue maintaining kgio for legacy purposes
indefinitely.

* homepage: https://bogomips.org/kgio/
* public mailing list: kgio-public@bogomips.org
* git clone git://bogomips.org/kgio.git
* Atom feed https://bogomips.org/kgio/NEWS.atom.xml
* mailing list archives: https://bogomips.org/kgio-public/

Changes: kgio 2.11.0 - reverting 2.10.0 breakage

    Mainly this release reverts back to kgio 2.9.3 behavior by
    supporting "autopush" functionality in the C extension.
    Removing this feature in 2.10.0 was a monumental mistake(*) on
    my part which caused a performance regression for ONE known user
    of kgio on the deprecated (but supported) Rainbows! server.

    This release does not affect known users outside of Rainbows!,
    but we may have unknown users, too.

    The attempt at a pure Ruby version of autopush had flaws and
    regressions in real-world testing, so that was abandoned.

    So yeah, kgio will be supported indefinitely even in the face
    of internal changes to MRI, but I strongly discourage its use
    for new projects.
    Users who only support Ruby 2.3 (and later) are encouraged to
    use `exception: false` with all *_nonblock methods.

    4 changes since 2.10.0:

          resurrect Kgio.autopush support in pure Ruby [REVERTED]
          reinstate the original (and dangerous) autopush in C
          TODO: update with Ruby 2.3 status
          test: increase test data sizes to fill socket buffers

    (*) - as was making this a separate project, at all

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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://bogomips.org/kgio/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161216-kgio-2.11.0-released@fail \
    --to=e@80x24.org \
    --cc=kgio-public@bogomips.org \
    --cc=ruby-talk@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

kgio RubyGem user+dev discussion/patches/pulls/bugs/help

Archives are clonable:
	git clone --mirror https://bogomips.org/kgio-public
	git clone --mirror http://ou63pmih66umazou.onion/kgio-public

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.lang.ruby.kgio
	nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.kgio

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git