Okay, I just checked some code and the delay makes no sense whatsoever to
me. Try taking it out. The only issue that it _might_ be related to (but it is
not clear to me how) is that incorrectly written client code might loop
endlessly under certain conditions if it does not check for errors during tight
loops of reading data. Because this has been a problem in some cases, I changed
the primitive to FAIL (instead of silently returning that no data has been
read).

In any case, the delay makes no sense. If there's a problem let me know but
make sure you got the latest VM.

Cheers,
  - Andreas

> > The 10ms delay (actually in the Socket code) is a workaround for the 
> > semaphore timeout seeming to hang occasionally at least on Windows.
> 
> Hm... a bit more information would be helpful. "seeming to hang
> occasionally" is not very descriptive. Does it hang? If so, where? What
> happens if you do
> a "print network state" from the VMs debug menu? Any particular test case
> where it does hang (even if occasionally)? Platforms this was found on?
> 
> Cheers,
>   - Andreas
> 

-- 
+++ GMX - Mail, Messaging & more  http://www.gmx.net +++
NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!