|Problems? Is your data what you think it is?|
Re: Help designing a threaded serviceby BrowserUk (Patriarch)
|on Jan 24, 2014 at 00:29 UTC ( #1071857=note: print w/replies, xml )||Need Help??|
What you've described sounds eminently doable. Though I'm going to question a couple of things and I'd probably make a few adjustments.
I think -- without being fully aware of your requirements -- that a better design would be to have the primary (listening) thread start dedicated thread(s) (one or two depending upon the answer to the above) for each client/command and accumulate the buffered output entirely local to that (those) threads.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In Section Seekers of Perl Wisdom