[ENet-discuss] Specification

[Lee Salzman]

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. :)

Lee

On 10/24/2010 07:29 AM, Tommi S.e. Laukkanen wrote:
> 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<lsalzman1 at cox.net>  wrote:
>
>    
>> ... Why?
>>
>> On 10/24/2010 02:44 AM, Tommi S.e. Laukkanen wrote:
>>      
>>> 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
>>>
>>>        
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cubik.org/pipermail/enet-discuss/attachments/20101024/f749e5bd/attachment.html>