Re^7: A suicidal parent OR death of a forking server (Use threads)

My example doesn't use a pool of threads. It starts a new thread for each connecting client.
For low levels of concurrency and long-lived connections this is more reliable.
It's about 50 lines of code with no need for the 300 lines of T::P::S, or the unnecessary 60 lines of T::S or Storable.
With complexity comes bugs.

But ultimately, it's your code, and if it's working for you and achieves the performance you require, that's great. Good luck.

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.

Comment on Re^7: A suicidal parent OR death of a forking server (Use threads)

Replies are listed 'Best First'.
Re^8: A suicidal parent OR death of a forking server (Use threads) by observer111 (Novice) on Jun 06, 2010 at 01:13 UTC
Follow up: All your comments were right on. I ended up ditching Thread::Pool::Simple for your even more simple pool of threads approach found here: http://www.perlmonks.org/?node_id=735931	[reply]
Re^9: A suicidal parent OR death of a forking server (Use threads) by BrowserUk (Patriarch) on Jun 06, 2010 at 11:08 UTC
Glad to have helped :) If your code isn't secret, or if it can be easily sanitised, care to post it here? Good (real) examples of threading are rare enough that every new example really helps to strengthen the knowledge base. 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. RIP an inspiration; A true Folk's Guy	[reply]