[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] process-fork weirdness
From: |
felix winkelmann |
Subject: |
Re: [Chicken-users] process-fork weirdness |
Date: |
Sun, 20 Mar 2005 14:17:16 +0100 |
On Thu, 17 Mar 2005 10:47:22 +0100, Peter Busser <address@hidden> wrote:
> Hi!
>
> > If the client tries to connect and the server isn't listening, the
> > connect -- and write -- will fail. Neither version is correct; the
> > second one just happens to work. You need to send some sort of message
> > -- a signal? -- from the server process to let the main program know
> > that it may begin connecting. You should do this after TCP-LISTEN but
> > before TCP-ACCEPT, which blocks.
>
> A simpler solution is to open the server socket before the forking and to
> close it in the client process.
>
You can also start the server in a different thread: tcp-accept does not
block other threads.
cheers,
felix