[DGD] Changing connect() (network package)

[bart at wotf.org]

On Wed, 2 Jan 2008 22:06:24 +0100, Felix A. Croes wrote
> 
> This won't always work because a signal at the wrong time will not
> be seen until later.  When there is no normal network input, DGD
> will sleep until the next callout is due; when there is no callout
> and no input from connections, DGD will sleep forever.  An interrupt
> just before it starts that long wait will not be seen until whenever
> the next execution round completes.

That reminds me, there is a bug in the nonblocking connect patch that I made
with regards to that. Fixed it, will make a patch available when I have time
later this week.

Bart
--
Created with Open WebMail at http://www.bartsplace.net/
Read my weblog at http://soapbox.bartsplace.net/