Here is a thought - I know you would resist a forked solution, but it seems to solve the issues in this problem domain. How about the main service (Process A) loop Fork off a process that handles the XML-HTTP/Soap etc (Process B).
Now, Process A can also be a client of Process B.
When we receive a Service termination request in Process A, we simply turn around and do a SOAP call to process B, asking it to please terminate. Then Process A terminates, and everyone dies happily.
(I dislike the idea of a cruel Infanticide, particularly when the victim is completely clueless why it is being killed.)
"When you are faced with a dilemma, might as well make dilemmanade.
"
-
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.
|