<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
<META content="MSHTML 6.00.2900.3698" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><FONT face=Arial size=2>If you do not specify either of these flags, the
default is unreliable but sequenced. If you specify the reliable flag, you
cannot use unsequenced and vise versa.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Kind regards,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Philip Bennefall</FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=nick@lifebloodnetworks.com
href="mailto:nick@lifebloodnetworks.com">Nicholas J Ingrassellino</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=enet-discuss@cubik.org
href="mailto:enet-discuss@cubik.org">enet-discuss@cubik.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, September 27, 2010 8:06
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [ENet-discuss] Mixing
Reliable and Unreliable and PacketOrdering</DIV>
<DIV><BR></DIV>Looking at the headers I only see
<I>ENET_PACKET_FLAG_RELIABLE</I> and <I>NET_PACKET_FLAG_UNSEQUENCED</I> for
<I>enet_packet_create()</I>. What am I missing?<BR>
<DIV class=moz-signature><BR>
<HR style="HEIGHT: 1px">
<P><SPAN style="FONT-WEIGHT: bold">Nicholas J Ingrassellino<BR><A
style="TEXT-DECORATION: none" href="http://www.lifebloodnetworks.com/"
target=_blank>LifebloodNetworks.com</A></SPAN> || <A
style="TEXT-DECORATION: none"
href="mailto:nick@lifebloodnetworks.com">nick@lifebloodnetworks.com</A></P>
<P style="FONT-SIZE: 75%">"<SPAN style="FONT-STYLE: italic">The idea that I
can be presented with a problem, set out to logically solve it with the tools
at hand, and wind up with a program that could not be legally used because
someone else followed the same logical steps some years ago and filed for a
patent on it is horrifying.</SPAN>"<BR>- <SPAN style="FONT-WEIGHT: bold">John
Carmack</SPAN> on software patents</P></DIV><BR>On 09/27/2010 01:36 PM, Philip
Bennefall wrote:
<BLOCKQUOTE cite=mid:013201cb5e6a$8505df50$0d00a8c0@philipe1dfe13a
type="cite">
<META content="MSHTML 6.00.2900.3698" name=GENERATOR>
<STYLE></STYLE>
<DIV><FONT face=Arial size=2>My understanding is as follows (anyone correct
me if I'm wrong here):</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>1. You'd first get the 100 unreliable packets,
exactly in the order you sent them but they are not all guaranteed to
arrive. You may get packets 1, 2, 3, 4, 6, but you will never get 1, 3, 2,
4.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>2. Then, you'd get the reliable packet
(guaranteed).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>3. After the reliable packet has been received
and acknowledged, you'd start receiving the remainder of the packets (which
is to say the 50 unreliable ones).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>In no event will you get packets in the wrong
order, as this is exactly what ENet is there to avoid. You can specify a
flag to get this behavior though, if you want it for whatever
reason.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Hope this helps.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Kind regards,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Philip Bennefall</FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,0) 2px solid; MARGIN-RIGHT: 0px">
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal; x-system-font: none">-----
Original Message ----- </DIV>
<DIV
style="BACKGROUND: rgb(228,228,228); FONT: 10pt arial; font-size-adjust: none; font-stretch: normal; x-system-font: none; moz-background-clip: border; moz-background-origin: padding; moz-background-inline-policy: continuous"><B>From:</B>
<A title=nick@lifebloodnetworks.com
href="mailto:nick@lifebloodnetworks.com" moz-do-not-send="true">Nicholas J
Ingrassellino</A> </DIV>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal; x-system-font: none"><B>To:</B>
<A title=enet-discuss@cubik.org href="mailto:enet-discuss@cubik.org"
moz-do-not-send="true">enet-discuss@cubik.org</A> </DIV>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal; x-system-font: none"><B>Sent:</B>
Monday, September 27, 2010 7:20 PM</DIV>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal; x-system-font: none"><B>Subject:</B>
[ENet-discuss] Mixing Reliable and Unreliable and Packet Ordering</DIV>
<DIV><BR></DIV>I know I could use different channels to get the result I
want but I was curious about the expected behavior using a single
channel.<BR><BR>Suppose if I had sent 100 unreliable packets, followed by
one reliable packet, followed by 50 more unreliable packets. In what order
should I expect them to arrive?<BR>
<UL>
<LI>Would I first get the 100 unreliable (in any order, if at all),
followed by the reliable, follows by the 50 unreliable (in any order, if
at all)?
<LI>Would I get these 151 packets in any order with only the reliable
one guaranteed to arrive? </LI></UL>I am also under the impression that
the second batch of 50 unreliable packets would not start to arrive (if at
all) until after the one reliable one has arrived?<BR>
<DIV class=moz-signature><BR>
<HR style="HEIGHT: 1px">
<P><SPAN style="FONT-WEIGHT: bold">Nicholas J Ingrassellino<BR><A
style="TEXT-DECORATION: none" href="http://www.lifebloodnetworks.com/"
target=_blank moz-do-not-send="true">LifebloodNetworks.com</A></SPAN> ||
<A style="TEXT-DECORATION: none" href="mailto:nick@lifebloodnetworks.com"
moz-do-not-send="true">nick@lifebloodnetworks.com</A></P>
<P style="FONT-SIZE: 75%">"<SPAN style="FONT-STYLE: italic">The idea that
I can be presented with a problem, set out to logically solve it with the
tools at hand, and wind up with a program that could not be legally used
because someone else followed the same logical steps some years ago and
filed for a patent on it is horrifying.</SPAN>"<BR>- <SPAN
style="FONT-WEIGHT: bold">John Carmack</SPAN> on software
patents</P></DIV></BLOCKQUOTE><PRE wrap=""><FIELDSET class=mimeAttachmentHeader></FIELDSET>
_______________________________________________
ENet-discuss mailing list
<A class=moz-txt-link-abbreviated href="mailto:ENet-discuss@cubik.org">ENet-discuss@cubik.org</A>
<A class=moz-txt-link-freetext href="http://lists.cubik.org/mailman/listinfo/enet-discuss">http://lists.cubik.org/mailman/listinfo/enet-discuss</A>
</PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>