And such a vitriolic comment profited this discussion how, exactly? Honestly, just cast your obligatory down-vote, as you customarily do, and leave it at that. Please keep your personal opinions to yourself. (On the other hand, I happen to strongly agree with the positive compliment that you were very rightly paid in the OP.)
Threads are a misunderstood and thus often-misused feature, no matter what language is being talked-about. The OP hit upon a textbook example of where threading is particularly well-suited, and obtained great results. All of his program’s requests were being served by another well-designed application of threading ... Apache. But how many times have we seen, even right here, situations where people fired off “one thread per request, regardless of transaction volume,” and wondered (publicly) why their server was being brought to its knees thereby? A good design in a suitable situation works consistently well, whereas one that is permitted to “hit the wall” is disastrously-bad (and negatively impacts the system as a whole). (In some cases it is literally a “fork bomb.”)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|