Skip to content
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

Signal handling. #86

Open
jmalloc opened this issue Mar 15, 2016 · 0 comments
Open

Signal handling. #86

jmalloc opened this issue Mar 15, 2016 · 0 comments
Assignees

Comments

@jmalloc
Copy link
Member

jmalloc commented Mar 15, 2016

Blocked by #85

Unlike streams, signal handlers need to be registered in an event-emitter like manner, otherwise signals could be missed if they arrive before the handler is re-registered (unless we always register handlers for all signals and buffer them, not sure of the performance impact there).

This could be accomplished with Recoil::callback() + pcntl_signal(), but it would be better if the kernel dispatched signals, probably when select() and equivalent is interrupted, as well as on a short-ish timer.

@jmalloc jmalloc added this to the 1.0.0 milestone Mar 15, 2016
@jmalloc jmalloc self-assigned this Mar 20, 2016
@jmalloc jmalloc modified the milestone: 1.0.0 Mar 20, 2016
@jmalloc jmalloc removed the blocked label Jan 4, 2017
@jmalloc jmalloc added this to the 1.0.0 milestone Jan 4, 2017
@jmalloc jmalloc removed this from the 1.0.0 milestone Oct 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant