Support both the console and browser equally

[nex3]

The http package should support IOClient and BrowserClient on even footing. "new http.Client()" should dynamically choose between them based on which is supported.

[nex3]

Marked this as being blocked by #6943.

[DartBot]

This comment was originally written by mi...@apaq.dk

---

This would be awesome.

In my particular case I'm building a client library for a Rest service. My first priority is to build a CLI application using the Client and for that purpose I will need to use the dart:io's HttpRequest. But I want to reuse the Client lib for a Web Interface later on and will then need to use dart:html's HttpRequest.

In order to make that work I have to build wrappers for each HttpRequests.

[nex3]

It's worth noting that you can use the http package on both the browser and the console today; you just need to explicitly choose to instantiate either an IOClient or a BrowserClient and pass it in to the code in question.

[DartBot]

This comment was originally written by mi...@apaq.dk

---

Huh. Why didn't I notice that until now? Please excuse a newbie. :)

Reading "http package" I was just thinking of some future http functionality - I didn't know it was a package that already existed. Thank you for guiding me.

[DartBot]

This issue has been moved to dart-lang/http#22.