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

Support Node >v0.10 #2

Open
thammi opened this issue Dec 1, 2015 · 3 comments
Open

Support Node >v0.10 #2

thammi opened this issue Dec 1, 2015 · 3 comments

Comments

@thammi
Copy link
Contributor

thammi commented Dec 1, 2015

Follow API changes which were introduced after v0.10. See #1.

@Globik
Copy link

Globik commented Sep 8, 2016

Hi thammi,
In TODO lists I see standing "get rid of the glib loop in its own thread".
Can you tell me please what does it mean? Why the glib loop is so bad? And how to make it in its own thread?

@thammi
Copy link
Contributor Author

thammi commented Sep 9, 2016

The library currently uses the glib event loop in its own thread to handle the i/o. The preferred way would be to integrate it into the event loop of Node.js/libuv. Having a seperate thread and event loop is kind of ugly and creates potential concurrency problems.

PS: Hijacking a ticket is not the preferred way of communication. Please open a new ticket next time or just send me an email.

@Globik
Copy link

Globik commented Oct 4, 2016

But node.js's libuv can't eat glib event loop.
Need rewrite ice components into the libuv?

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

2 participants