libuv fully refactored #564
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As I did for the
LibBoostAsioHandler, I also completely rewrote theLibUvHandler, and the related test example code.The new handler is perfectly in line with those of
libboostasioandlibev, in terms of implemented features and reliability. After all, those are the inspirations.This definitely fixes #516 as the heartbeat now works, and #491 is probably fixed as well. Among the peculiar characteristics of this handler there is certainly speed. At the end, native Libuv is polling.
I'm making this version of the handler available here, along with the example test, for anyone who wants to try it out in advance or take a look inside.
Important
libuv_2025-12-20.zip
@ogapo, I hope you don't mind, but your implementation was way behind the times.