feat: introduce internal exporter http client #3577
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
Introduce an internal http client that chooses the available http implementations in
XMLHttpRequest
,fetch
,sendBeacon
, andnode:http
based on feature detection. The http client is designed to be used with exporters only. The exposed HTTP Client is a feature-limited one. Exporters don't care about the response details of the request.This enables exporters to support environments like Deno, ServiceWorker, that don't support
XMLHttpRequest
orsendBeacon
. And reduces the duplications between exporters.Type of change
How Has This Been Tested?
Checklist: