At 22:31 24/05/2012, you wrote:
Really the best way to do this sort of server pinging is just to
hack into enet_protocol_receive_incoming_commands, and use some
distinguished invalid peer ID to identify packets that you dispatch
to your app via a callback into it or what not.
I know it's somewhat easy, especially when you know well how
everything works, that's why I tried to tempt you to do it... ;-)
I didn't think about using the peerID like that, it's a good hint.
Tomorrow, I'll give a try to that, and see how it goes... Almost 50%
of my network code I have to port is actually linked to handling that
server info, thus my need to have something clear & efficient about
this feature. The other stuff is easier as it's almost all in ENet already.
_______________________________________________
ENet-discuss mailing list
[email protected]
http://lists.cubik.org/mailman/listinfo/enet-discuss
