select is definitely how I would do it, for several key reasons:
- It is architecturally uncomplicated: the process is actually doing only one thing at a time, even though it is unpredictable what it might do next.
- You never have to worry about things being incomplete ... about accidentally sending someone a partial-message that you haven’t finished reading yet.
- You can easily prioritize what it is doing, according to the business requirement.
- Messy timing issues are generally avoided completely.
The program itself is really a dispatcher, connected to everything else with nice, flexible pipes and sockets. It goes to sleep, wakes up with a “honey-do list,” does its chores in whatever sequence it best sees fit, then goes back to sleep again. As long as none of these things take a significant time to actually do, esp. relative to the others, it all works great.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||