From: Jean-Francois Nadeau <jean-francois.nadeau@...>
Date: 2004-07-13T22:08:50+09:00
Subject: Re: UPDATE - [PATCH] Nonblocking socket connect - Win32 - 181

Hi all,

What's the status of this patch?

Thanks,

Jean-Francois Nadeau
http://www.jfnadeau.com

> -----Original Message-----
> From: U.Nakamura [mailto:usa@garbagecollect.jp]
> Sent: Thursday, July 08, 2004 2:05 AM
> To: ruby-core@ruby-lang.org
> Subject: Re: UPDATE - [PATCH] Nonblocking socket connect - Win32 - 181
> 
> Hello,
> 
> In message "Re: UPDATE - [PATCH] Nonblocking socket connect - Win32 - 181"
>     on Jul.08,2004 11:33:13, <jean-francois.nadeau@sympatico.ca> wrote:
> | I now call rb_thread_select in a loop and when the "except" fd is set, I
> | check for a socket error using getsockopt. If I get no error, I loop
> back on
> | rb_thread_select. At the end of the process, I finally get an error code
> | from getsockopt and then, I return the error to ruby.
> |
> | If you have an explanation for this behavior, please tell me, I am very
> | interested to know the answer.
> 
> Thank you!
> 
> I've modified the patch for CVS HEAD, with nobu's help.
> On this new patch, all platforms use wait_connectable() -- derived
> from thread_w32_connect_select() -- instead of thread_write_select().
> Can I commit this patch, Matz?
> 
> 
> Regards,
> --
> U.Nakamura <usa@garbagecollect.jp>