fzzbt/radix — pull request #20 by smw1218 (2012-10-03 21:58:17+00:00)
Title: Adding a full retry on read failure

This is my fix for issue #19 but it's maybe not the optimal solution. Summary: I attempt full request retry on non-timeout socket errors. This means that I go back and perform the write again, which runs the init code to reconnect the dropped connection. I only attempt retry once and only on failure of the first read of a request.

I ignored retry for the read in subscription.go since that code was wrapped differently and I am not familiar with that redis feature. It should at least continue to work the same as it does now.

I also ignore retry on multibulk subsequent reads but that is probably the right thing to do since the first read should be the one that fails under normal dropped connection circumstances.