Alexey Ovchinnikov

Ah, sorry - I've forgotten to resend data after reconnection - some additional fixes needed

Now all works fine in my environment. What should I do with test coverage? ) Where are no any tests related to `Elixir.Connection` behaviour in `client_test.exs`.. Should I implement some...

> However would using `:inet.setopts(sock, active: :once)` in the client process allow us to handle idle disconnect earlier and not have to retry a request? We should usually get a...

@fishcakez I'm ready for your re-review )

> I wonder if handling the disconnect immediately (active: true with message handling) is enough for the issue you're seeing as we would catch scenario 1) most of the time...

@fishcakez I've kept `active: true` and remove resending logic. Ready to review

Hi, guys! I need a SASL authentication for hbase. I can prepare another PR with auth backend support, but I need this PR to be included in my code too...

@fishcakez ready to review )

@jparise is it enough to add: > The `:reconnect` option if setted to `true` forces client to reopen tcp connection whenever it closed. as a last paragraph to the end...

@hogart because I want to keep data bindings in code (not in templates)