Sounds like an ideal application of threads.
One or more receiver threads receive and enqueue the message + timestamp in memory. One or more sender threads, read the queue, and check the timestamp, drop any passed their sellby and forward them whereever.
You can overlap the network delays of both receiving and sending, and tailor the number of senders and recievers as the project evolve using command line parameters.
One process, with say 3 receivers and 6 senders and no middleman DB could probably saturate 1-mb bandwidth with maybe 15% cpu on a 2GHz machine.
If you have higher bandwaidth available, change 2 numbers and you match the requirements.
It's simple, flexible and very scalable.
Examine what is said, not who speaks.
Silence betokens consent.
Love the truth but pardon error.
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! —
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.