<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>When you send an unreliable message, Enet will
allocate some memory, put it in the outgoing command list, and wait until an
enet_host_service() call is made, right? Is this for the benefit of
throttling? In the case where there is no throttling, waiting until an
enet_host_service() call is made can cost several milliseconds in latency, not
to mention some load in memory allocation and fragmentation. A small
degredation in performance has been noticed on local networks since Enet
has been integrated. Pings are generally higher, including some 10ms
pings, which is unusual. Is it possible to have an interface to send the
message immediately?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Side note: I'm not too keen on the
heavy run-time memory allocation. It would be nice to have some
options for pre-allocating an array of buffers.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Tim Auld<BR>Lead Programmer<BR>Ratbag <BR>Level 8,
63 Pirie Street, Adelaide SA 5000, Australia<BR>Ph 08 8223 5830, Fax 08 8223
5746, Mobile 0413 660 994<BR>email <A
href="mailto:tim@ratbaggames.com">tim@ratbaggames.com</A><BR>Website <A
href="http://www.ratbaggames.com">www.ratbaggames.com</A><BR> <BR>This
email is confidential for the addresse only and is subject to<BR>copyright where
applicable.</FONT></DIV></BODY></HTML>