Hi,

> From: "Wilson Bilkovich" <wilsonb / gmail.com>
> On 8/26/05, Tanaka Akira <akr / m17n.org> wrote:
> > In article <033601c5a9fa$26ba7840$6442a8c0@musicbox>,
> >   "Bill Kelly" <billk / cts.com> writes:
> > 
> > > The blocking I/O issues are the thorniest problem for me
> > > writing applications in ruby.  (Of course, it's 1000 times
> > > worse on Windows, ... where nonblocking I/O is apparently not
> > > supported at all yet.  That is just a nightmare.)
> > 
> > I heard Windows has nonblocking I/O for sockets.
> 
> Windows actually has plenty of support for nonblocking operations on
> sockets and files.
> Here's an example hit from MSDN:
> http://msdn.microsoft.com/library/en-us/ipc/base/named_pipe_type_read_and_wait_modes.asp

Thanks; I should have been more clear... I'd posted earlier
this year, in
http://ruby-talk.org/cgi-bin/scat.rb/ruby/ruby-talk/138533
about a way to put windows sockets into nonblocking mode.

What I meant by "nightmare" is that few (if any) nonblocking
operations in windows are supported in ruby.

One thing I've wondered, is if a win32 socket were put into
nonblocking mode via a C extension (I notice ruby's win32.c
already defines a rb_w32_ioctlsocket() ... but nothing seems
to use it) ... Would ruby's scheduler on win32 work correctly
with windows sockets in nonblocking mode?  I haven't tried
this yet.


Regards,

Bill