<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I think the 86 seconds it would take you to add to YOUR very
specific packet handling code is not worth adding a whole bunch of
irrelevant data to the wrapper itself.<br>
<br>
Take for example profiling your networking, Some questions you might
ask :<br>
How much data are chat message taking up in my game?<br>
How much data is spent keeping players in sync (versus say, how
much is sent administering players)?<br>
How much data is spent on player joining, just player joining
(ie all players lag when someone joins).<br>
<br>
NONE of this can be answered by ENet, and never should be. <br>
"Simple statistics" mean nothing, and if you want a total byte count
just increment a single variable.<br>
<br>
<br>
On 2010/10/21 04:21 PM, Nicholas J Ingrassellino wrote:
<blockquote cite="mid:4CC04C81.2030800@lifebloodnetworks.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On the one hand I understand-- and love-- the idea of the
minimalistic
approach. Sure, it was designed for games, but if you want a
lobby, or
compression, or encryption, you have to implement it yourself.
These
are all high-level functions that keep ENet light on its feet and
would
be better implemented if trailered for a specific game. Bandwidth
tracking, however, I feel would be best if part of the ENet API.
If for
no other reason than ENet can let us know about overhead in
addition to
the raw data being sent. Hell, it already reports latency.<br>
<div class="moz-signature"><br>
<hr style="height: 1px;">
<p><span style="font-weight: bold;">Nicholas J Ingrassellino<br>
<a moz-do-not-send="true" style="text-decoration: none;"
href="http://www.lifebloodnetworks.com/" target="_blank">LifebloodNetworks.com</a></span>
|| <a moz-do-not-send="true" 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 10/21/2010 09:43 AM, Beau Albiston wrote:
<blockquote
cite="mid:C122A00A717EF443A4D6D9A3CF36017E0C3EC89F@ALMail01.totimm.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);">It
would be nice to have some statistics functions. I would
be
most interested in things like bytes/sec sent/received at
the socket,
for
instance.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);">-Beau<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-style: solid none none; border-color:
rgb(181, 196, 223) -moz-use-text-color
-moz-use-text-color; border-width: 1pt medium medium;
padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif"; color:
windowtext;">From:</span></b><span style="font-size:
10pt; font-family:
"Tahoma","sans-serif"; color:
windowtext;">
<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:enet-discuss-bounces@cubik.org">enet-discuss-bounces@cubik.org</a>
[<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="mailto:enet-discuss-bounces@cubik.org">mailto:enet-discuss-bounces@cubik.org</a>]
<b>On Behalf Of </b>Nicholas
J
Ingrassellino<br>
<b>Sent:</b> Thursday, October 21, 2010 8:16 AM<br>
<b>To:</b> Discussion of the ENet library<br>
<b>Subject:</b> Re: [ENet-discuss] Bandwidth
Monitoring?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ooohhh, I misunderstood their purpose. Is
there
a variable
somewhere that will tell me how much data is going back and
forth at
any given
time or do I need to do that myself?<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" style="text-align: center;"
align="center">
<hr size="1" align="center" width="100%"></div>
<p><b>Nicholas J Ingrassellino<br>
<a moz-do-not-send="true"
href="http://www.lifebloodnetworks.com/"
target="_blank"><span style="text-decoration: none;">LifebloodNetworks.com</span></a></b>
|| <a moz-do-not-send="true"
href="mailto:nick@lifebloodnetworks.com"><span
style="text-decoration: none;">nick@lifebloodnetworks.com</span></a><o:p></o:p></p>
<p><span style="font-size: 9pt;">"<i>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.</i>"<br>
- <b>John Carmack</b> on software patents<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><br>
On 10/20/2010 10:19 PM, Lee Salzman wrote: <o:p></o:p></p>
<p class="MsoNormal">They're never updated and merely hold the
values
you pass in
when you create the host.<br>
<br>
Lee<br>
<br>
On 10/19/2010 10:13 AM, Nicholas J Ingrassellino wrote: <o:p></o:p></p>
<p class="MsoNormal">Is there something special I have to do
to get <i>_ENetPeer.incomingBandwidth</i>
and <i>_ENetPeer.outgoingBandwidth</i> working? I am using
both
reliable and
unreliable packets but these values are always zero. For
example, if I
do <i>std::cout
<< event.peer->incomingBandwidth;</i> inside my
main loop I
get
bumpkis.<i> </i>Also, how often are they updated?<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" style="text-align: center;"
align="center">
<hr size="1" align="center" width="100%"></div>
<p><b>Nicholas J Ingrassellino<br>
<a moz-do-not-send="true"
href="http://www.lifebloodnetworks.com/"
target="_blank"><span style="text-decoration: none;">LifebloodNetworks.com</span></a></b>
|| <a moz-do-not-send="true"
href="mailto:nick@lifebloodnetworks.com"><span
style="text-decoration: none;">nick@lifebloodnetworks.com</span></a><o:p></o:p></p>
<p><span style="font-size: 9pt;">"<i>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.</i>"<br>
- <b>John Carmack</b> on software patents<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>ENet-discuss mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:ENet-discuss@cubik.org">ENet-discuss@cubik.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://lists.cubik.org/mailman/listinfo/enet-discuss">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
</div>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
ENet-discuss mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:ENet-discuss@cubik.org">ENet-discuss@cubik.org</a>
<a moz-do-not-send="true" 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>
<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>
<br>
</body>
</html>