Re: [Chicken-users] busy-wait in tcp-connect

[felix winkelmann]

I have pushed a new version that hopefully fixes, what was wrong with
tcp-connect: the select was always performed for input. But a connect
to a *server* that expects input (so the connect must actually call select
for output) was endlessly waiting (but at least not busy...).
I have changed this now to wait for both input or output. Normal
client and server code seems to work ok, now. Please give it a try.


cheers,
felix