ENet does not really have support for behavior like this built-in. All reliable packets follow the same time-out scheme, and if no ack ever gets received the connection is just... disconnected.
You'd basically have to emulate it with unreliable packets and ack them on your end if you want some more application specific behavior. On 02/10/2012 06:13 PM, Yan Luo wrote:
Hello, Is there a way to specify the attempt timeout for sending reliable message? Here is the scenario: * message A needs to be sent reliably to host X. * message A is sent by enet and the attempt continues until an ACK is received from the destination node (that is what I understand how enet would behave). * However, in my application, message A becomes stale (or even harmful) if it is in the sending host for over N milliseconds: there is no need to keep sending it any more. How should I implement such a scenario? Thanks in advance for the help. Yan
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
