Let's see. You have a 100 slaves and one master. The master needs to collect data from each slave once a minute. Does the master always collect a piece of data per minute per slave? If so, it is not obvious why you need the master to initiate the connections; you could implement this as a regular server that waits for incoming connections. It just needs to be aware of how many clients it has, total, and keep track of which ones have fallen out of schedule.
100 TCP connections a minute sounds quite moderate; any intranet webserver has to manage more.
May I ask what it is you're trying to do? If it's a monitoring script, you needn't reinvent the wheel; there are very capable packages like Nagios (formerly NetSaint), mon and Big Brother freely available for the job.
Makeshifts last the longest.
In reply to Re: Unusual(?) server
by Aristotle
in thread Unusual(?) server
by Nygeve
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |