How about using an agreed-upon socket (port number) for listen()ing on, and then just structure the code like any other networking server code -- fork the socket/process on connect, parent listens for more connections, child services the current connection/request(s).. As a side benefit, this allows the client/server to be on different network nodes if ever desired, like during testing..

?