There is also an ability to flush based on a certain peer I believe...<br><br>I would think that certain real time data would be desirable to flush right away to the peer... <br><br>Then remaining packets could be picked up at some interval...<br>
<br><div class="gmail_quote">On Wed, Jan 7, 2009 at 5:47 PM, Nuno Silva <span dir="ltr"><<a href="mailto:little.coding.fox@gmail.com">little.coding.fox@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On the docs it said that enet_host_flush() is also supposed to send all queued packets (for sending), although it wont treat events like enet_host_flush(), so if the OP just wants to send various packets and not wait for enet_host_service(), he could use enet_host_flush() instead.<div>
<div></div><div class="Wj3C7c"><br>
<br><div class="gmail_quote">On Thu, Jan 8, 2009 at 6:29 AM, Lee Salzman <span dir="ltr"><<a href="mailto:lsalzman1@cox.net" target="_blank">lsalzman1@cox.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This all depends on what is acceptable latency for you and how often you are sending packets. Packets are sent out when you call enet_host_service(), so schedule this according to your needs.<br><font color="#888888">
<br>
Lee</font><div><div></div><div><br>
<br>
Peter Soxberger wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In what periods should enet_host_service() be called? I'm using a thread and alwas wait 2 milliseconds until I call enet_host_service(). Should I wait longer? What are your typical periods?<br>
<br>
Greets,<br>
Peter Soxberger<br>
<br>
-------- Original-Nachricht --------<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Datum: Wed, 07 Jan 2009 20:11:06 -0800<br>
Von: Lee Salzman <<a href="mailto:lsalzman1@cox.net" target="_blank">lsalzman1@cox.net</a>><br>
An: Discussion of the ENet library <<a href="mailto:enet-discuss@cubik.org" target="_blank">enet-discuss@cubik.org</a>><br>
Betreff: Re: [ENet-discuss] Enet Header size<br>
<br>
</blockquote>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It collects packets in between calls to enet_host_service(), yes.<br>
<br>
Lee<br>
<br>
Peter Soxberger wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ok does this mean that ENet collects the small packets and send it as<br>
<br>
</blockquote>
one big packet for saving overhead?<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I worried that this isn't implented because I use a lot of packets with<br>
<br>
</blockquote>
small data in them and this would produce a lot of unnecessary overhead.<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-------- Original-Nachricht --------<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Datum: Wed, 07 Jan 2009 19:18:15 -0800<br>
Von: Lee Salzman <<a href="mailto:lsalzman1@cox.net" target="_blank">lsalzman1@cox.net</a>><br>
An: Discussion of the ENet library <<a href="mailto:enet-discuss@cubik.org" target="_blank">enet-discuss@cubik.org</a>><br>
Betreff: Re: [ENet-discuss] Enet Header size<br>
<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The size of a header for an individual user packet WITHIN a protocol packet is about 6-8 bytes. Each protocol packet (which groups as many user packets as it can up to the MTU) has a header size of 8 bytes.<br>
<br>
Lee<br>
<br>
Peter Soxberger wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi!<br>
<br>
I'm currently improving my code that calculates the actual<br>
<br>
</blockquote></blockquote></blockquote>
transferrate.<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
</blockquote>
Does anybody of you know, how much overhead I produce if I send a<br>
<br>
</blockquote></blockquote>
single<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
packet? I know that there is the UDP Header which is 8 Byte big. But<br>
<br>
</blockquote></blockquote>
how<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
much is used by ENet?<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If I calculate the real size of a packet, is this correct:<br>
<br>
[UDP Header]+[ENet Headers]+[packet->dataLength] = Packet Size<br>
<br>
Thanks for your help!<br>
<br>
</blockquote>
_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org" target="_blank">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
<br>
</blockquote>
<br>
</blockquote>
_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org" target="_blank">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org" target="_blank">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
<br></blockquote></div><br>