Missing Elasticsearch.Net.Connection.HttpClient NuGet package

[maximpashuk]

From RC1 release, there are 3 implementations of IConnection available:

Elasticsearch.Net.Connection.HttpConnection
Elasticsearch.Net.Connection.Thrift.ThriftConnection
Elasticsearch.Net.Connection.HttpClientConnection

@Mpdreamz I am not sure about your plans about last implementation, should it be always used instead of HttpConnection or not.

Anyway at this time last implementation are not provided with NuGet package - separate package like Elasticsearch.Net.Connection.Thrift or as a part of NEST package.

Please provide last implementation of IConnection by NuGet package

[maximpashuk]

I just thought that my my issue can be related with #725, since HttpClient class is 4.5-specific and not available in 4.0.

[Mpdreamz]

@maximpashuk good catch we will publish Elasticsearch.Net.Connection.HttpClientConnection package when we publish 1.0.

As it stands now HttpClientConnection does not offer any real benefit see the original PR for it here:

#663

That does not mean the work that @renevo did is in fain. Moving forward we are heavily interested in actual different HttpMessageHandlers such as

https://github.com/abock/CurlSharp
https://github.com/trustme/LibCurlDotNet
https://github.com/masroore/CurlSharp

Or even start actively committing our own/helping an exisiting library out. The default HttpMessageHandler in HttpClient still uses WebRequests like the default IConnection that NEST uses does though.

The HttpConnection IConnection implementation that comes with NEST and Elasticsearch.NET is still recommended since its what we use in all our integration tests and performance profiling sessions.

Leaving this issue open as a reminder that we also need to publish this dll as separate nuget package. Thanks for the heads up @maximpashuk 👍

[maximpashuk]

Then package will be uploaded to nuget.org ?