[ENet-discuss] ENet and transient network failures

[Ruud van Gaal]

See also enet.h:

   ENET_PEER_TIMEOUT_MINIMUM              = 5000,
   ENET_PEER_TIMEOUT_MAXIMUM              = 30000,

Not sure what the minimum means anymore; normally I'd assume here that
indeed 30000 ms (30 s) is the timeout.

Ruud

On Thu, Aug 11, 2011 at 4:07 PM, Jay Sprenkle <jsprenkle at gmail.com> wrote:

> On Thu, Aug 11, 2011 at 8:54 AM, Pontus Bergsten <pontus_bergsten at yahoo.se
> > wrote:
>
>> Consider the case when two ENet nodes communicates over a network where
>> transient failures are common, e.g. a bad WiFi connection.
>>
>> If one node receives a DISCONNECT event from ENet, is one guaranteed that
>> the disconnected remote node will also receive a DISCONNECT event?
>>
>> Or is there a possibility that one ENet node could consider the connection
>> broken for a short while, while the other node will consider the connection
>> alive during the transient network outage?
>>
>
>
> This is always a problem for anything using a network. There's nothing
> specific to ENet or networking. If a system crashes/gets physically
> disconnected then the ENet library will time out and consider the system
> disconnected. I believe the time is set to 30 seconds by default.
>
>
>
> ---
> "There's a zombie outbreak!  Oh, no, wait a second...  It's just a bunch of
> kids texting."
>
> _______________________________________________
> ENet-discuss mailing list
> ENet-discuss at cubik.org
> http://lists.cubik.org/mailman/listinfo/enet-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cubik.org/pipermail/enet-discuss/attachments/20110811/c5a88d30/attachment.html>