Deprecate WavefrontProxyClient [WIP]

[laullon]

Addresses Issue #46

[vikramraman]

@laullon At a high level, here's what we need to do:

• Add a construct similar to WavefrontClientFactory
• Add a WavefrontMultiClient
• Latest versions of the proxy support receiving all atoms (metrics, histograms, spans etc) using a single port over HTTP. So we will deprecate the existing Proxy and Direct senders in favor of the new WavefrontClientFactory.

Since both the proxy and direct ingestion will be over HTTP going forward, the configuration for both is similar barring the URL endpoint (batchsize, queuesize, flushinterval etc apply to both). And it will be backed by a singular WavefrontClient

[vikramraman]

A lot of the changes break backwards compatibility. It'd be nice to retain backwards compatibility as much as possible.

[vikramraman]

Added some more comments.

[vikramraman]

lgtm!

[randallt]

How can I use the new Sender that only takes a URL? Looks like

import (
	wfsender "github.com/wavefronthq/wavefront-sdk-go/senders"
)

func InitTracing(serviceName string, applicationName string) wfsender.Sender {
	sender, err := wfsender.NewSender("http://wfproxy.wavefront:2878")
	if err != nil {
		panic(err)
	}
	return sender
}

currently doesn't work, as NewSender is undefined.

[laullon]

This is not yet released, if you want to test it make sure you point your dependencies to master branch.

[randallt]

@laullon is there a timeline to release this?