package:http should be recommended over dart:io's HttpClient

[brianquinlan]

Page URL

https://api.dart.dev/stable/2.19.2/dart-io/HttpClient-class.html

Page source

No response

Describe the problem

We want to promote using package:http instead of the HttpClient that is part of dart:io (see the plan)

Expected fix

Ideally we would:

• Create a better landing package for package:http that:
  • Explains the value of the package
  • Explains how to choose a Client implementation (maybe a feature table for IOClient, cronet_http, cupertino_http, fetch_client etc.)
  • Explain how to configure the Client (per isolate, --dart-define=no_default_http_client=true, etc.)
  • Explains how to use package:http with Flutter (e.g. don't use Network.image)
  • Maybe point to package:dio?
• Modify the HttpClient page to make it more clear that users should use package:http
• Remove the reference to HttpClient in the library tour

Additional context

Relevant existing pages:

• dart:io HttpClient
• Flutter Networking
• Flutter Cookbook: Networking
• Dart tutorials: Fetch data from the internet

[brianquinlan]

I have the outline of some documentation.

Maybe it would make sense to put this in the package:http site somewhere since it cuts across flutter and dart?