Given the short transmissions and very simple connect/request/response/close nature of your connections; this application cries out for being written using non-blocking sockets and a select loop.
Forking a process (or spawning a thread) to handle such short-lived transactions simply doesn't seem necessary.
I'd offer some code or a reference to some, but as you've mentioned both *nix and windows and haven't identified where your proxy will run...
In reply to Re: Bidirectional Client/Server - to fork or not to fork?
by BrowserUk
in thread Bidirectional Client/Server - to fork or not to fork?
by ljamison
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |