Client configuration for streaming connections about reboot HOT 5 CLOSED

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

from reboot.

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.

from reboot.

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!

from reboot.

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?

from reboot.

None in my eyes.

from reboot.