[#7872] Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...>

All, I needed a nonblocking socket connect for my asynchronous-event

18 messages 2006/05/14
[#7873] Re: Nonblocking socket-connect — Tanaka Akira <akr@...17n.org> 2006/05/14

In article <3a94cf510605140559l7baa0205le341dac4f47d424b@mail.gmail.com>,

[#7874] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

How about introducing the method Socket#set_nonblocking, or alternatively

[#7875] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,

[#7876] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

Well, it's ok then. I'm comfortable adding in the nonblocking

[#7877] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,

[ ruby-Patches-4464 ] Better error messages in OpenSSL::SSL.[accept, connect]

From: noreply@...
Date: 2006-05-13 06:58:56 UTC
List: ruby-core #7868
Patches item #4464, was opened at 2006-05-13 06:58
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1700&aid=4464&group_id=426

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Technorama Ltd. (technorama)
Assigned to: Nobody (None)
Summary: Better error messages in OpenSSL::SSL.[accept, connect]

Initial Comment:
Show a useful error message in SSL.accept and SSL.connect.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1700&aid=4464&group_id=426

In This Thread

Prev Next