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...
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.