[ENet-discuss] ENet 2.0 most wanted features?
Mark Palkow
palkow at daviko.com
Tue Apr 30 07:36:52 PDT 2013
It would be nice to have a flag ENET_PACKET_FLAG_SEMI_RELIABLE
Meaning enet will try to resend such packets only once in case it got not
ack.
Von: enet-discuss-bounces at cubik.org [mailto:enet-discuss-bounces at cubik.org]
Im Auftrag von Lee Salzman
Gesendet: Dienstag, 30. April 2013 11:44
An: Discussion of the ENet library
Betreff: [ENet-discuss] ENet 2.0 most wanted features?
So, I'm just thinking in the back of my mind what sort of things would be
desired in a hypothetical version 2.0 of ENet that broke API compatibility
and so could do things that would otherwise not be possible in a 1.x
release.
That doesn't mean that a 2.0 is in the near future, but I'd like to get a
dialogue going about it.
Aside from IPv6 support, are there any other big things people would want
that are none-the-less realistic and not overly complicated?
More information about the ENet-discuss
mailing list