The only practical way that I have ever found to determine whether a client has crashed is to oblige the protocol between the two to periodically send a “heartbeat” message if there is nothing else to be sent during some mutually agreed-upon interval. The host should record the latest timestamp as each socket sends a message, or just a boolean flag, and use a periodic timer, say about half-again as long as the heartbeat, to check for absence of response within that time. Upon which the host might presume that the client is dead. You see, you really can’t be 100% sure, AFAIK, that all of the intermediates between here-and-there are still in good working order. Maybe the host knows that the socket has been closed or that communication has failed, or maybe it doesn’t. But if a bottle washes up on shore, even if it’s empty, you know the sender is still out there.
-
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.
|