[ENet-discuss] timeout for attempting to send a reliable message

Dennis Schridde devurandom at gmx.net
Sun Feb 12 10:26:07 PST 2012


Am Sonntag, 12. Februar 2012, 13:36:24 schrieb Benoit Germain:
> 2012/2/12 Yan Luo <yanluo.uml at gmail.com>
> > 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?
> 
> And an correlated request: please consider making all the internal
> ENet timeouts part of some structure whose contents default to the
> current hardcoded values, but that we can change if necessary (for
> example, when debugging, it is *very* desirable to have a large
> disconnect timeout so that we don't get disconnected each time we
> inspect code when hitting a breakpoint).
+1

I seriously considered rewriting my code, to put the network part into a 
background thread, so that I could debug the software with valgrind.

--Dennis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.cubik.org/pipermail/enet-discuss/attachments/20120212/f72a5a61/attachment.pgp>


More information about the ENet-discuss mailing list