New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design: kqueue and windows "power user" interfaces #26

njsmith opened this Issue Jan 22, 2017 · 1 comment


None yet
1 participant

njsmith commented Jan 22, 2017

Haven't really been thought through, need a good look over

@njsmith njsmith changed the title from Design: kqueue "power user" interface to Design: kqueue and windows "power user" interfaces Feb 13, 2017


This comment has been minimized.


njsmith commented Feb 13, 2017

One definite change is that instead of returning a new UnboundedQueue, these should have you pass in an existing UnboundedQueue. This allows multiple event streams to be multiplexed onto a single queue. (In the Windows case this also means our completion event objects should include the completion key as a field.) See #40.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment