a4db630ba7
=== kgio 2.11.0 - reverting 2.10.0 breakage / 2016-12-16 22:56 UTC
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
6 lines
384 B
Text
6 lines
384 B
Text
$NetBSD: distinfo,v 1.10 2017/03/12 14:38:17 taca Exp $
|
|
|
|
SHA1 (kgio-2.11.0.gem) = 4b31817f69a2efed9ba9c800c98c747a54a0f434
|
|
RMD160 (kgio-2.11.0.gem) = c0b106a313d90b1950d564405280f9ec6a7fad5d
|
|
SHA512 (kgio-2.11.0.gem) = aa5146e596ca8ca434b23edb780a64a39955f3d5c68c00746a5f0aae48b801dd06e5aa14b7456978ed80048a7c5ee2cd497c942054e08ffc46b724d4d8bce473
|
|
Size (kgio-2.11.0.gem) = 59392 bytes
|