This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 20
Implement timeouts for requests to backend #18
Milestone
Comments
This looks to be something that will be native to tokio-proto. |
Now that we moved to hyper, waiting for this to be implemented and then we just need to use it. |
Moving to 0.2 milestone as we wait for hyper. |
Moving to 0.3 milestone as we wait for hyper. |
I tried to implement this. Unfortunately, https://github.com/sfackler/hyper-timeout-connector works for |
Waiting on hyperium/hyper#1234 |
hjr3
added a commit
that referenced
this issue
Jul 15, 2017
- hyper-timeout allows connect, read and write timeouts - updated Config with timeout values - refactor the way the worker is started Fixes #18
hjr3
added a commit
that referenced
this issue
Jul 15, 2017
- hyper-timeout allows connect, read and write timeouts - updated Config with timeout values - refactor the way the worker is started Fixes #18
hjr3
added a commit
that referenced
this issue
Jul 15, 2017
- hyper-timeout allows connect, read and write timeouts - updated Config with timeout values - refactor the way the worker is started Fixes #18
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There is no timeout when sending a request to the backend. This is probably blocked by #16 and may need to be discussed with people in the tokio irc channel.
The text was updated successfully, but these errors were encountered: