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

Tying an event's lifecycle to the thread that created it sucks #10

Open
msullivan opened this issue Feb 17, 2012 · 0 comments
Open

Tying an event's lifecycle to the thread that created it sucks #10

msullivan opened this issue Feb 17, 2012 · 0 comments

Comments

@msullivan
Copy link
Owner

Currently, threads track the events that they created and when they exit, free the events and the associated file descriptors. Same with buffers. This is kind of lame, since it means that you can't hand events/buffers to newly created threads. On the other hand, it's a really easy way to automatically clean up the events/buffers/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant