Great. This sounds like the perfect library for my application.
I am streaming currency rates using TCP at the moment; the client is at
an arbitrary
IP address on the internet. To maintain "real time" streaming, the
packet size is small,
so the TCP header size / packet size is quite large. The connection must
be reliable.
It looks like ENet would give me a better header/payload ratio.
Thanks!
Aaron
Lee Salzman wrote:
The library was developed and tuned for 56K modem usage, perhaps which is
sort of a joke in this day and age. :)
There is no particular roadmap for new features. The library has just
grown stuff
as Sauerbraten has needed the features. Thus, it tends to be rather
stable over
time, and it's even pretty safe to fork the code or do whatever with
it rather than
treat it as a normal library because of that.
Lee
Aaron Boxer wrote:
Thanks. How much testing has been done under high packet loss?
Also, in general, what are the known issues with the library?
Is there a roadmap for new features?
Thanks again
Lee Salzman wrote:
It uses pings or reliable packets to measure the mean round trip
time for the connection.
Any excessive deviation from this causes a throttle to oscillate up
or down, which regulates
how often ENet will drop unreliable packets to reduce bandwidth usage.
Lee
_______________________________________________
ENet-discuss mailing list
[email protected]
http://lists.cubik.org/mailman/listinfo/enet-discuss
_______________________________________________
ENet-discuss mailing list
[email protected]
http://lists.cubik.org/mailman/listinfo/enet-discuss
