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

[felix winkelmann]

On 5/22/07, Dan Muresan <address@hidden> wrote:
> >> While we're on the topic, I find Chicken's lightweight-threads and
> >> srfi-18 compatible streams incredibly useful. However, it's a pity that
> >> only unit tcp (and the (process) function) can create such streams.
> >
> > I assume you mean streams that block the current thread on I/O, yes?
> > That shouldn't be a problem as long as you have an fd and can make it
> > non-blocking.
>
> Yes, streams that block the current thread on I/O. Are you saying that I
> can already create such streams from an fd? How?

Kon has recently added ##sys#custom-[input|output]-port to the
posix unix which sound like they are useful (Kon, can you say
something about these?)

You can also look at the nbstdin egg, which has a "nonblocking-input-port"
procedure.


cheers,
felix