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

Tokio support #6

Open
lilianmoraru opened this issue May 21, 2017 · 1 comment
Open

Tokio support #6

lilianmoraru opened this issue May 21, 2017 · 1 comment

Comments

@lilianmoraru
Copy link

Plans to switch from mio to tokio?
This would make scaproust play nice with the async ecosystem(also compiling the code throws a lot of deprecation warnings).

@blabaere
Copy link
Owner

I've been scratching my head about this for quite some time now (see the TODO.MD file) and I think this really needs to be done, for a lot of reasons. The problem is:

  • I don't see yet how to implement load-balancing and fair queuing with tokio the way they are in nanomsg. That's because mio readiness events are not exposed via tokio.
  • I almost don't have time at the moment for side projects and switching to tokio is a big change.

When I'll have some time, I will probably create a new library over tokio rather than changing scaproust. It will probably be closer to mango and less like the original C API.

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