Closed
Description
Instead of HTTPSTransport and HTTPTransport that both delegate all of the work to the parent class, what if there is only a single transport that can do HTTP and HTTPS?
The distinction now seems artificial, unlike @sentry/browser that has two transports, one based on fetch and the other on XmlHttpRequest.