Hmm.

The problem I see is this:

Either using referenceCount or freeCallback, just going on destruction, there is no way to know why the packet was destroyed. ENet not needing it any more might just mean a disconnection as well. Or what about enet_host_broadcast (C# Host.Broadcast)? It sends to many different peers. So what does it really tell you about delivery for ENet to delete it?

If it is good enough for you to know that ENet didn't need it any more, the Packet structure's NativeData property can be used to get the low-level ENet structure. That has referenceCount and freeCallback (for example, IntPtr refCount = p.NativeData->referenceCount, though you will need to enable unsafe code in your project). referenceCount does say internal use only as well...

As for freeCallback, I could add helper functions to register callbacks on freeing, easy, but I worry it is incomplete for the reasons mentioned above.

Your thoughts?

James

On 2/25/2013 2:09 PM, BS Flasher wrote:
Thanks James,
Your work is so great and is complete for me. But a little another thing. Can you add a method for checking the delivery of a reliable packet in sender (or a help for me to add that) ?

On Sun, Feb 24, 2013 at 4:45 PM, James Bellinger <[email protected] <mailto:[email protected]>> wrote:

    Howdy,

    I've got one at:

    http://www.zer7.com/software.php?page=enetcs

    You can also get it on NuGet, but that package doesn't have
    samples and has only XML documentation not a help file.
    Either way, it includes a sample that echoes data back and forth
    between a client and server.

    The bindings are presently compiled for 32-bit, so you'll need to
    go to Target CPU and choose x86.
    By 'can't compile that', do you need a .sln for a particular
    version of Visual Studio, or...?

    James


    On 2/24/2013 2:59 AM, BS Flasher wrote:

        Hi,
        Can anyone send me a compiled dll (or ready project) for enet
        1.3.6 in
        .net framework 2?
        I can't compile that.

        Thanks
        _______________________________________________
        ENet-discuss mailing list
        [email protected] <mailto:[email protected]>
        http://lists.cubik.org/mailman/listinfo/enet-discuss


    _______________________________________________
    ENet-discuss mailing list
    [email protected] <mailto:[email protected]>
    http://lists.cubik.org/mailman/listinfo/enet-discuss




_______________________________________________
ENet-discuss mailing list
[email protected]
http://lists.cubik.org/mailman/listinfo/enet-discuss

_______________________________________________
ENet-discuss mailing list
[email protected]
http://lists.cubik.org/mailman/listinfo/enet-discuss

Reply via email to