Variations in ping time to each client means you can't send something to all of them simultaneously, regardless of the local hardware limitations. Multiple processes won't help you there.

If you just want to make sure you're sending the same data to everyone from a rapidly changing source, copy the file(s) to a temp folder (or read into memory), then distribute that temp copy to the clients.

A single threaded application can send single packets to each ready client in turn so no one of them will hog all the bandwidth or unduly delay the others. If your single app doesn't let any client get more than one packet ahead of the others, then you can keep them all in synch up to the last packet at the cost of having a bad client slowing everybody down.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.