HTTP Client for Exporters

[hekike]

Using the raw Node Core HTTP client comes with some functionality questions.
For example, do we need to consider implementing the followings:

• Following redirect
• Configurable timeout
• Retry logic
• Authentication / Configurable HTTP headers

Do we want to use a third-party npm library and maybe expose it's configuration to the user or should we go with the built-in http.request and implement these features incrementally based on user requests?

cc @mayurkale22 I think you will face the same questions with the Jaeger exporter.

[draffensperger]

Another question related to this: do we care about the Zipkin exporter working for the web? Typically I would think the exporter story for the web should just be to export to the OpenTelemetry agent and then have it handle actual exporters, but I figured I'd ask.

[mayurkale22]

Typically I would think the exporter story for the web should just be to export to the OpenTelemetry agent and then have it handle actual exporters.

This makes sense to me and I'd prefer this route.

[danielkhan]

In SIG meeting 2019-08-14 it was concluded that this should be the responsibility of the package.

Closing. Please reopen if you disagree. FYI @hekike