<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
What about tracking clients? I am unclear about how to tell who is who.<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 08/26/2010 07:35 PM, Lee Salzman wrote:
<blockquote cite="mid:4C76FA41.5030202@cox.net" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
ENET_PACKET_FLAG_RELIABLE is for reliable and sequenced, there is no
way to get reliability without sequencing in ENet.<br>
ENET_PACKET_FLAG_UNSEQUENCED is for unreliable and unsequenced
currently. It gets ignored if reliable is used.<br>
If you simply pass in neither of these flags, you get UNreliable and
unsequenced, i.e. pass in 0 for the flags.<br>
<br>
These flags are passed in to enet_packet_create(), which determines the
type of packet.<br>
<br>
Lee<br>
<br>
On 08/26/2010 02:26 PM, Nicholas J Ingrassellino wrote:
<blockquote cite="mid:4C76DC0D.8070106@lifebloodnetworks.com"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
I am pretty new to the <b>ENet</b> library (and network programming in
general). I have done a few test games with <b>HawkNL</b> but that is
about all and was at least one year ago.<br>
<br>
With the help of the <b>ENet</b> tutorial on the site I have built a
server and client that can
pass data back and forth (I was so happy). The tutorial, however, has
left at least two things unclear to me:<br>
<ol>
<li>How can I send data reliably but unsequenced? How can I send
data
unreliably but sequenced?<br>
</li>
<li>How can I track connections when more than one client is
connected?</li>
</ol>
I know there are <i>ENET_PACKET_FLAG_RELIABLE</i> and <i>ENET_PACKET_FLAG_UNSEQUENCED</i>
via the headers. The tutorial does not when mention <i>ENET_PACKET_FLAG_UNSEQUENCED</i>
nor its expected behavior so I am left to assume. Judging by the
variable names I think these are meant to be used in bit flags? I have
also noticed that <i>ENetEvent->peer</i> has a few members that
might be what I am looking for when tracking connections (<i>outgoingPeerID</i>,
<i>incomingPeerID</i>, <i>connectID</i>, <i>outgoingSessionID</i>,
<i>incomingSessionID</i>)
but
I am unclear on which of these to use if any.<br>
<div class="moz-signature"><br>
<hr style="height: 1px;">
<p><span style="font-weight: bold;">Nicholas J Ingrassellino</span><br>
</p>
<p style="font-size: 75%;"><span style="font-style: italic;"></span><span
style="font-weight: bold;"></span><br>
</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>
</body>
</html>