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
Client configuration for streaming connections #30
Comments
I feel like making the dispatch Defaults public would help a bit. Otherwise, those providing builders are going to have to resort to the same kind of copy and paste code |
Since "reboot" has built in support for streams it makes sense to me that it should be easier for new users to make use of this feature without resorting to investigate the source code of dispatch and API of async-http-client. Changing Defaults is a step in the right direction though. |
Geez guys, can't Dispatch keep anything private? :) I didn't have time to come up with a great Defaults interface for 0.9.3 and needed some freedom to redo it in the future. There should really be a method on Http for building on the default configuration. I'll push some code here in a bit. With 0.9.3 you'll have to live with some config boilerplate, but at least it's forwards-compatible config boilerplate! |
Also now that I'm aware of this issue I'm inclined to default to not having a request timeout. Any thoughts on the downsides of that? |
None in my eyes. |
Currently if you create a streaming connection it defaults to timeout after 60000 ms. In order to override it you must pass a client which is configured to not timeout:
It would be nice to make this setting more streamlined in a similar way to how promise timeout is set.
Unless there is an easier way I am not aware of that is...
The text was updated successfully, but these errors were encountered: