Was the packet lost or just delivered after 2 seconds? After a dozens of hours I would suspect the operating system ( memory management ). If it were ENet it would probably have been seen much faster.
On Mon, Jun 6, 2011 at 8:12 PM, czj <[email protected]> wrote: > Hello, > i found that the "ENET_PACKET_FLAG_RELIABLE " FLAG can't guarantee . > Use default config.A Peer( as Client) send a RELIABLE packet to another > peer( as Server) every 2 sceond. > after dozens of hours,the connection between client and server is time out. > > Client and Server Run at same PC. > > the client's history: > 2011-6-3 17:59:00 Heatbeat... > 2011-6-3 17:59:02 Heatbeat... > 2011-6-3 17:59:04 Heatbeat... > > the server's history: > 2011-6-3 17:59:00 Client:10.1.1.1:18988 Heatbeat... > 2011-6-3 17:59:02 Client:10.1.1.1:18988 Heatbeat... > 2011-6-3 17:59:12 Client:10.1.1.1:18988 TimeOut!!! > > it's seemed that the packet sent from client at 2011-6-3 17:59:04 can't be > received by server. > > Any Idea?? > > > 2011-06-07 > ------------------------------ > czj > > _______________________________________________ > ENet-discuss mailing list > [email protected] > http://lists.cubik.org/mailman/listinfo/enet-discuss > > -- --- "There's a zombie outbreak! Oh, no, wait a second... It's just a bunch of kids texting."
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
