Zachary Anker

You should be able to look at ‘cause’ on the exception to get the superclass if you want to contextually retry. Sent from my iPhone > On Feb 21, 2018,...

SGs Sent from my iPhone > On Dec 12, 2015, at 07:12, Erik Michaels-Ober [email protected] wrote: > > — > Reply to this email directly or view it on GitHub.

Yea I'd like to work on Socketry but it looks like I'll not have time for a while :(

@tarcieri do you remember what broke with Celluloid::IO? I thought it was due to the timeout portions, we could just make a Celluloid timeout class for people to use I...

It's pretty easy to do, but I'm probably not going to have time to do it this week. I can take a look next week @msufa.

I think it was somewhat reasonable to not support keyword arguments in 2015. Given it's now 2018, and Ruby 2 was obsoleted for almost two years, I don't think there's...

Oh did we bump the min? I missed that sorry! Then we absolutely should move to keyword arguments.

We support `CONNECT` proxying, which only supports HTTP (to the proxy). I don't believe we support SOCKs proxies? It's been a while since I've messed with a SOCK proxy though.

It looks like the docs are out of date, and the proper syntax is `HTTP.timeout(3)`. I've updated them to use that. Is that clearer now?

Ack, sorry. I forgot that a 4.0 version is on master at this point. The API is fixed in 4.0, but the reason it requires the awkward setup of calling...