kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: "Iñaki Baz Castillo" <>
Subject: Re: Like OpenSSL::SSL::SSLSocket#connect_nonblock
Date: Tue, 10 Apr 2012 23:55:04 +0200	[thread overview]
Message-ID: <> (raw)

2012/4/10 Eric Wong <>:
> Iñaki Baz Castillo <> wrote:
>> Hi, I include a patch fixing the doc typos. More inline:
> I meant a proper git commit via git format-patch (with commit message,
> properly crediting you) so I can just pipe the entire email (or
> attachment[1]) to "git am".

Hope it has been properly received in a separate mail :)

>> I've worked too much (yet) with Ruby OpenSSL bindings, but I hope that
>> it does allow setting my own verification method.

Here I meant: "I've NOT worked..." :)

> It might be best to come up with working code for Ruby OpenSSL bindings
> first.  It's better-supported, at least.

Ok, what I'm doing is a Gem for using Ruby sockets within
EventMachine. For now I've created the TcpClient (which depends on
Kgio::TCPSocket). Next step is TlsClient. Current code:

So ok, first I'll try Ruby OpenSSL (managing EAGAIN exception during
the TLS handshake) and once it works I'll try Kgio-monkey :)

> I've never considered kgio-monkey production-ready, but it should be
> mostly compatible and easy to switch between the two libraries (the
> long-term goal has always been to move things developed in
> kgio/kgio-monkey into Ruby upstream).


Thanks a lot.

Iñaki Baz Castillo

      reply	other threads:[~2012-04-10 21:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 21:50 Like OpenSSL::SSL::SSLSocket#connect_nonblock Iñaki Baz Castillo
2012-04-09  3:22 ` Eric Wong
2012-04-09 18:31   ` Iñaki Baz Castillo
2012-04-09 18:44     ` Iñaki Baz Castillo
2012-04-10 20:26       ` Eric Wong
2012-04-10 20:50         ` Iñaki Baz Castillo
2012-04-10 21:02           ` Eric Wong
2012-04-10 21:55             ` Iñaki Baz Castillo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).