in reply to IO:Socket question... sort of :)
There are obviously multiple ways to design a solution to your problem. I would suggest viewing multiple code snippets using the "Super Search" functionality of this website and borrowing outrageously from your favorite(s). I tried a mundane search of ("tcp" "multiple" "server") and found lots of potentials.
I doubt that performance is an overriding concern for your purposes, but benchmarking others' code would also lend insights into the optimal approach for your architecture (perldoc benchmark).
|
|---|