Thanks! Simple solutions are the best. Pablo
On Tue, Jun 23, 2015 at 3:45 PM, <[email protected]> wrote: > I've investigated this further and is seems like the problem occurs when > the server side gets two connect commands, ENET_PROTOCOL_COMMAND_CONNECT > from the same client without any disconnect in between. The ENet host at > the server will in that case get two peers with the exact same address and > port. After a while one of them will get a timeout, and that timeout is > what triggers the strange ENET_EVENT_TYPE_DISCONNECT. Our application > code at the server side interprets this as a connection loss, but on the > client side it is still connected since we have that other peer still up > and running and responding. > > I've solved this by letting the application code on the server do a reset > on the current peer when a new is received with the same address and port. > > >
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
