Are your "very good reasons" good enough to justify
using a threading implementation which is experimental and
is known not to be thread-safe?
You haven't said what you are doing, but my strong
recommendation is to use an existing solution, such as
Apache with mod_perl.
As for your problem, the best way I can think of to solve
it with threading is to split the child thread into 2.
One to write back to the client, one to wait a fixed time,
and if the page is still loading send a timeout message
and then close the connection. (The backend work still
gets done either way.) Hope and pray that you don't have
a race between when the sleeper starts writing its timeout
message and when the other thread chooses to finish what
it is doing...
-
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.
|