From: gabriele renzi <surrender_it@...1.vip.ukl.yahoo.com>
Date: 2003-09-25T01:39:20+09:00
Subject: Re: When threads block

il Wed, 24 Sep 2003 11:26:47 +0200, "Thomas Sondergaard"
<thomas@FirstNameGoesHereSondergaard.com> ha scritto::

>> If you use Windows, it's a known problem but hard to fix with
>> current thread implementation.
>
>When will we get a new thread implementation, then? :-)
>
>Seriously, could you outline how these things are implemented on other
>platforms to avoid blocking the entire process? Why can't this trick be used
>on the windows platform? I'd like to help if I can in any way.

The problem should be related to windows' select().
On *nix IO stuff is transparently put in a select, and ruby takes care
of giving a little time to every thread when select gives them output.
On windows this won't work cause select() just accepts socket
descriptor. I wonder if these works in python. 
And is WaitForMultipleObjects() useful someway ?

>Another question - is true thread safety on the TODO list for ruby? Oh and
>this begs the third question: Is there a release plan for ruby? I would love
>to know what kind of goodies I can expect for future releases?

wait for Rite (ruby 2.0)