Thanks for the reply. A follow up question, what is "default time-out scheme" of ENet? How many times or how long does ENet try to resend an undelivered reliable message? > >Message: 2 >Date: Fri, 10 Feb 2012 13:41:46 +0200 >From: Lee Salzman <[email protected]> >To: Discussion of the ENet library <[email protected]> >Subject: Re: [ENet-discuss] timeout for attempting to send a reliable > message >Message-ID: <[email protected]> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >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 > > >End of ENet-discuss Digest, Vol 105, Issue 1 >********************************************
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
