<!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 text="#c0c0c0" bgcolor="#000000">
I think the particular strength of ENet is that it is a small library
of code that is free to change as one pleases for various goals. I
think a standard or otherwise rigid specification is antagonistic to
this goal. ENet is not a perfect or all-encompassing library, so the
main effect would be to just enshrine its faults irrevocably on paper,
and also that it would create more hassle for the one developer
(singular) of ENet than it is actually worth. :)<br>
<br>
Lee<br>
<br>
On 10/24/2010 07:29 AM, Tommi S.e. Laukkanen wrote:
<blockquote cite="mid:B0FD895E-FFC7-4F55-B5D9-505D3E091908@gmail.com"
type="cite">
<pre wrap="">This particular case I have in mind is protocol for virtual worlds in IEEE.
Best regards,
Tommi Laukkanen
On 24.10.2010, at 14.58, Lee Salzman <a class="moz-txt-link-rfc2396E" href="mailto:lsalzman1@cox.net"><lsalzman1@cox.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">... Why?
On 10/24/2010 02:44 AM, Tommi S.e. Laukkanen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Hi
Would it be possible that one of the ENET developers would write description document of the enet in wire protocol and algorithms involved so ENET could be proposed as a protocol and implementation library to standards?
Best regards,
Tommi Laukkanen
</pre>
</blockquote>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>