Not everyone uses Linux and I come from OpenTNL where this kind of
simulation really is useful.
You can call it the OSs responsibility all you want, it doesn't really
matter. Streaming is too high level for ENet too, yet it's requested.
On 2013-04-30 17:16, Shaun Reich wrote:
packet loss simulation and latency are all something your OS (if it
isn't completely shitty), should be able to do. in the case of windows
you need to go through a lot of extra work to do it. in the case of
linux it's 2 short commands. there's no point in duplicating and
wasting effort on that, which is the job of the OS itself...
as for ENET_PACKET_FLAG_SEMI_RELIABLE, i'm wondering in which cases
one would actually want to use that?
NAT hole punching is definitely not something not-so-difficult. And
there are other libs out there that are meant for it that can be
integrated into your network handling.
"As a follow up I meant that it would allow us to simulate packet
drops and packet sending speed. Also allowing to simulate a % for
packet drop and packet sending through some parameter to the Host
would be just as good if it's too complicated!"
again, that's your operating system's job, not a job for a networking library.
--
Shaun Reich,
KDE Software Developer (kde.org)
_______________________________________________
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
