-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
cannot use with tokio::run() #20
Comments
Here's a test program that doesn't respond to incoming requests. You can connect to it like so:
|
And here's a program that doesn't use a threadpool properly. You can test this program with: Expected behavior: this command completes in about 1s.
|
Thanks for reporting the issue @njaard. I'm open to pull requests if you have ideas for the api you'd like to see. |
There's no way I could write you a patch, because my understanding of tokio is too poor. I guess there should be an Api that provides a |
That's cool. I can dig into this. Thanks for the sample code. I'll try an use this example code under the examples dir when I figure this out |
There's no way to get Futures from incoming connections. Plain old hyper uses this kind of code:
But hyperlocal doesn't allow it. Even if you do
into_future()
(after mapping the outputs to()
), then it doesn't work because it never actually processes requests.This feature is necessary because hyperlocal's event loop doesn't work at all with threadpooling and the
tokio_threadpool::blocking
function.The text was updated successfully, but these errors were encountered: