ENet behaves sanely if you make a malloc callback that returns NULL, and there 
is also a protocol constant for setting a maximum packet size.

On 09/01/2012 07:16 PM, progmars wrote:
Hi all.
I have found a blog article which mentions some important but easy to implement 
improvements (already done by the author of the blog):
http://www.leadwerks.com/werkspace/blog/50/entry-248-enet-modifications/
This article is two years old, so I would like to know, if some of those 
suggestions have already been implemented in the Enet library itself, and I 
don't need to bother about memory failure management and packet size limitation 
issues?

Martin


P.S. For some reason Enet-discuss did not accept emails from inbox.lv domain, I got 
"Undelivered mail returned to sender" messages.
I had to reregister from gmail.com...


_______________________________________________
ENet-discuss mailing list
[email protected]
http://lists.cubik.org/mailman/listinfo/enet-discuss

Reply via email to