On May 30, 2007, at 8:21 , J J wrote:

> From: tim Rowledge <tim at rowledge.org>
>> Reply-To: The general-purpose Squeak developers list<squeak- 
>> dev at lists.squeakfoundation.org>
>> To: The general-purpose Squeak developers list<squeak- 
>> dev at lists.squeakfoundation.org>
>> Subject: Re: Alternative Thread Schedulers
>> Date: Tue, 29 May 2007 13:48:07 -0700
>>
>> Not as such, no. *IF* you implement the io in such a way that it  
>> can  be non-blocking (see the somewhat mouldy AsynchFile class for  
>> an  example) then you would indeed make the relevant thread/ 
>> Process yield  by way of waiting on a semaphore.
>
> Oh sorry, missed this part in my response.  Actually, this is  
> exactly what I *don't* want.  I don't want to jump through special  
> hoops doing IO just to play nice with scheduling, I want it to be  
> that way by default like in the OS.  Sounds like I may have more  
> work cut out for me then I thought. :)

This referred to file i/o. If I am not mistaken, socket i/o actually  
uses delays and semaphores a lot.

- Bert -