Jan-Erik Rediger

I do understand the friction it will cause due to config file changes. I'd like to test this a bit further, including proper tests and IPv6 support. Happy to work...

For some reason the connection to Redis breaks. Maybe because of timeouts or because your network has hiccups. Unlikely that it's the code's fault

There are still some useful things in there, but I need to pick them out one-by-one (or rebase-and-fix)

Thanks, will check again (though the many newly introduced line-breaks make this a little bit more difficult)

Sure, it's running on free heroku, so it hasn't the most resources, but it should be fine.

Fine with me. Maybe @itamarhaber can set me up with a bigger instance. Hosting the application on my server would be fine, just not Redis itself. :)

Well, I could run the application on my own server, so EU based would be great. Will do the signup tomorrow or friday.

Hey @BBCMarkMcDonnell. We maitain redis-rb in our free time and may not face the same problems as heavy users. Looks like this issue just fell through. @hale's fix was never...

IMO it was a mistake to even handle the environment variable at all. It is always better to let the user pass this explicitely. But indeed, if the user passes...

Uhm, we already support block-less transactions: ``` [2] pry(main)> r.multi => "OK" [3] pry(main)> r.set "foo", "bar" => "QUEUED" [4] pry(main)> r.get "foo" => "QUEUED" [5] pry(main)> r.exec => ["OK",...