| commit | 333347c3ae54c8d605c673fcd11ff8dcb2ea4c38 | |
| author | Eric Wong <e@80x24.org> | |
| Thu, 15 Dec 2016 22:53:48 +0000 (15 22:53 +0000) | ||
| committer | Eric Wong <e@80x24.org> | |
| Thu, 15 Dec 2016 23:51:08 +0000 (15 23:51 +0000) | ||
| tree | 0663faa01cb9f84457a1b55ab52867ed986dd64c | treesnapshot (tar.gz zip) |
| parent | 64dc570f4b99f68b5ed792b36e7e8abc3df74927 | commitdiff |
reinstate the original (and dangerous) autopush in C
The regression for existing users was unnacceptable and
completely poor judgement on my part. This change brings
us back to potentially not-future-compatible code which
will impose maintenance burdens on us in the face of
future Ruby changes.
But TODAY, it is the most performant option for folks who
need to use autopush.
Revert "resurrect Kgio.autopush support in pure Ruby"
and "remove autopush support and make it a no-op"
This reverts commits 64dc570f4b99f68b5ed792b36e7e8abc3df74927
and 4347980fa66115425fa8b765353c8b1bfe5dec24.
The regression for existing users was unnacceptable and
completely poor judgement on my part. This change brings
us back to potentially not-future-compatible code which
will impose maintenance burdens on us in the face of
future Ruby changes.
But TODAY, it is the most performant option for folks who
need to use autopush.
Revert "resurrect Kgio.autopush support in pure Ruby"
and "remove autopush support and make it a no-op"
This reverts commits 64dc570f4b99f68b5ed792b36e7e8abc3df74927
and 4347980fa66115425fa8b765353c8b1bfe5dec24.
14 files changed: