Migrate to the `fetch` API

[natebosch]

dart2js will stop supporting internet explorer soon - so all supported browser should support fetch which allows for streaming. I'm not sure if streaming works on firefox so that will need to be tested.

https://api.dart.dev/stable/2.13.4/dart-html/Window/fetch.html

http/lib/src/browser_client.dart

Lines 27 to 29 in f93c76f

	/// [BaseRequest.followRedirects], and [BaseRequest.maxRedirects] fields. It is
	/// also unable to stream requests or responses; a request will only be sent and
	/// a response will only be returned once all the data is available.

[pedia]

How about this since one year past?

[jtmcdole]

This would be a good feature request for us. Happy to take a look and see how well it maps.

[natebosch]

Example of using fetch in Dart: https://github.com/dart-lang/dartdoc/blob/f0d2cbf5f517d936d01a61e7350147e3ad12edb9/web/search.dart#L35

[pedia]

We need cross all platform fetch. e.g. long polling http request, come from here
It's called from package:http/http.

[srix55]

Looks like we need to fallback on websockets. Flutter web's http (BrowserClient) has no streaming capability. EventSources have their own issues (no http headers, for starters). That's a huge minus. Fetch, QUIC, web-transport, http3 are still years away. websockets it is.

[jtmcdole]

Looks like we need to fallback on websockets. Flutter web's http (BrowserClient) has no streaming capability. EventSources have their own issues (no http headers, for starters). That's a huge minus. Fetch, QUIC, web-transport, http3 are still years away. websockets it is.

what about web-rtc?

[kaoet]

Bump this thread. There is no XHR in Chrome manifest v3 service workers so fetch must be used there instead of XHR. https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/#background-service-workers