Request timeout #51
Closed
Request timeout #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
diogob
force-pushed
the
timeout
branch
2 times, most recently
from
bbf4ad2
to
e684752
Compare
diogob
changed the title
|
I am still going to give |
|
closed in favour of #52 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea is to be able to configure a timeout for every call of a service (or fetcher).
This avoids the awkward code necessary to configure a timeout for each request.
It makes sense since the timeout usually is a trait of the target server (the same for several endpoints).
We should still allow the same API to be used on an individual request.