<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="" text="">Hi Lee, <br>
<br>
I have some time to revisit the issue again.Both server/client are on my
machine, so it can take up to 30 secs for the disconnection to be
received when either side crashes. I would assume the timing would be
shorter, like under 5 seconds.<br>
<br>
<br>
Robin<br>
<br>
<br>
<pre wrap=""><div class="moz-txt-sig">>The amount of time it takes to disconnect depends on the measured
>round-trip-time, which is an indication of how laggy the connection
>is. Disconnect is not supposed to take a fixed time.
On Wed, Jul 12, 2017 at 12:31 AM, Robin <a class="moz-txt-link-rfc2396E" href="mailto:imtrobin@gmail.com"><imtrobin@gmail.com></a> wrote:
</div></pre>
<blockquote type="cite" style="color: rgb(0, 0, 0);"><pre wrap="">Hi,
When I crash the server (for testing), I notice the time for client to
receive the disconnection message, can vary between 5 seconds to 30 seconds.
I'm tried various timeout in both server/client (in the while loop) e.g
enet_host_service (EnetClient_, &event, 0);
enet_host_service (EnetClient_, &event, 30);
This happens even on both server/client running on local server. I would
expect it to be consistent timing, but this is varying too big. Is there
somewhere to debug this?
--
Robin</pre></blockquote>
</body></html>