As is, the roundTripTimeout for outgoing commands are doubled . The problem I see with this is that as time passes, you're less likely to have success simply due to fewer and fewer resends. Even if this command is finally successfully sent, it may be considerably delayed and if the command is ordered then every command behind it will be delayed as well. Depending on the peer's roundTripTime, this could take very few resends to cause the connection to drop with the default peer timeoutMinimum.
It seems like it would be better to simply resend with a 'normal' timeout to increase the chance of success. Particularly with ordered data, as it is the most important command and therefore should get higher priority resend and not lower. -- Best regards, Mike mailto:[email protected] _______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
