-
Notifications
You must be signed in to change notification settings - Fork 366
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
Handle timeouts in BrowserClient #136
Conversation
Also remove stale [docs] link. Closes dart-lang#3
Copy components from shelf
Enable pub run test
Merge 0.11.x branch
In the example, `Client` and `BaseClient` are package qualified, but `BaseRequest` and `StreamedResponse` aren't.
At this point, we're only using this for Chain.current which might as well just be StackTrace.current.
What's the benefit to exposing this as a client-specific context variable rather than providing client-agnostic middleware? |
The functionality is already built-in with the web platform in this case. A client middleware could use configuration specific imports to choose either the |
What's the benefit of using the built-in behavior, though?
I don't understand. How would it know what the implementation of the root-level client is? |
Adds support for
HttpRequest.timeout
as well as catching the timeout event.Closes #21 at least for
BrowserClient
.