Not to mention you'd have the same issue if the users' network was disconnected suddently.<br><br><div class="gmail_quote">On Thu, Nov 5, 2009 at 5:27 PM, Alain Becam <span dir="ltr"><<a href="mailto:Al@thegiantball.com">Al@thegiantball.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><pre>Hi,</pre><pre> Thank you for your answer! Actually when they disconnect properly, there is no problem. It is in case of crash that we have this problem. Unfortunately it happens ;)</pre>
<pre>//Alain</pre><pre>Hi Alain,
Is it possible for your peers to send a disconnection message before going
away ?
regards,
Ju
On Thu, Nov 5, 2009 at 2:03 PM, Alain Becam <<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">Al at thegiantball.com</a>> wrote:
><i> Hello,
</i><div><div></div><div class="h5">><i> Greetings from a new happy user. We are using ENet has the "low-level"
</i>><i> communication API for an object-oriented solution, with object replication.
</i>><i> Thanks for this great library !
</i>><i>
</i>><i> Mostly for debug purposes, we increased the TIME_OUT, like that:
</i>><i>
</i>><i> ENET_PEER_TIMEOUT_LIMIT = 3200, // 32
</i>><i> ENET_PEER_TIMEOUT_MINIMUM = 5000, // 5000
</i>><i> ENET_PEER_TIMEOUT_MAXIMUM = 300000, // 30000
</i>><i>
</i>><i> It works well to avoid too quick disconnections, but we still have a
</i>><i> problem. When a new peer connect, it receives the list of existing peers
</i>><i> from the server, then try to connect to all peers, and when done, send an
</i>><i> acknowledgment to the server. Then the server replicates the existing
</i>><i> objects. But with these time-out, a disconnected peer is discovered after a
</i>><i> very long time, and if a new peer connect, it will never send the ack to the
</i>><i> server (because he is waiting for the connection and until it receives the
</i>><i> disconnection event).
</i>><i>
</i>><i> We tried to do that in protocol.c (line 1270):
</i>><i>
</i>><i> outgoingCommand -> roundTripTimeoutLimit = (ENET_PEER_TIMEOUT_LIMIT/100) *
</i>><i> outgoingCommand -> roundTripTimeout;
</i>><i>
</i>><i> But it seems to have some nasty side-effects (when some communications are
</i>><i> occurring, it might disconnect very quickly again)...
</i>><i>
</i>><i> Any way to have a quick disconnection and still a long time-out for comms ?
</i>><i>
</i>><i> Kind regards,
</i>><i> Alain
</i>><i>
</i></div></div>><i> _______________________________________________
</i>><i> ENet-discuss mailing list
</i>><i> <a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">ENet-discuss at cubik.org</a>
</i>><i> <a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a>
</i>><i>
</i>><i>
</i></pre><br>
<br>_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
<br></blockquote></div><br>