Peers are by default pinged every 500ms internally which is also subject to this timeout. See enet_peer_ping_interval() if this is still too long for you.
On Wed, Apr 17, 2013 at 1:43 PM, Sebastian Ahlman < [email protected]> wrote: > Say I have to processes running ENet, one server and one client. Neither > one is sending any application specific data across the wire, but they do > have an active ENet connection. If one of the processes crashes (or I kill > it) the other one will, after some time, realize that the other peer went > away and I will get a disconnect event on the process that is still active. > I would like to adjust the timeout so that the remaining process realizes > this almost immediately, say in two seconds or so. I found the function > enet_peer_timeout(), but that seems to deal with ACKs to reliable packets, > and I want to have the system react to lost connections without me having > to send reliable packets. Clearly this already works, but it takes too long > for my purposes. Can I make the timeout smaller somehow? > > Thanks! > > _______________________________________________ > ENet-discuss mailing list > [email protected] > http://lists.cubik.org/mailman/listinfo/enet-discuss > >
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
