From: Eric Wong <firstname.lastname@example.org> To: email@example.com, firstname.lastname@example.org Subject: [ANN] kgio 2.11.0 - legacy I/O for legacy Ruby + Unix Date: Fri, 16 Dec 2016 23:18:37 +0000 [thread overview] 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: email@example.com * 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 other threads:[~2016-12-16 23:18 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [ANN] kgio 2.11.0 - legacy I/O for legacy Ruby + Unix' \ /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
Code repositories for project(s) associated with this inbox: ../../kgio.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).