<div dir="ltr">If you do this:<div><br></div><div>- peer1: send data packet with ID x, adds 'x' to a list of unacknowledged packets</div><div>- peer2: receives data packet x, sends back packet 'ACK<x>' to peer1.</div><div>- peer1: As soon as ACK<x> arrives, clears that ID in the list of unacknowledges packets.</div><div>- peer1: based on the same list, resend packets that have not been ACK'ed yet and are >t old. Keeps a counter of how many resends have been done.</div><div><br></div><div>The main problem should be the ordering of data packets on the other side.</div><div><br></div><div>Ruud</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 12, 2016 at 12:15 PM, Elshad Mustafayev <span dir="ltr"><<a href="mailto:elshad@goubiq.com" target="_blank">elshad@goubiq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">But how can I do that? Does enet let me know what packets are lost? And is there an easy api that would let me ask for retransmission of the lost packet?<div><br></div><div>Or how easy is it to change enet's source so that we can specify maximum retransmission trial for reliable packets?</div><div><br></div><div>Thanks.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 12, 2016 at 12:00 AM, <span dir="ltr"><<a href="mailto:enet-discuss-request@cubik.org" target="_blank">enet-discuss-request@cubik.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send ENet-discuss mailing list submissions to<br>
<a href="mailto:enet-discuss@cubik.org" target="_blank">enet-discuss@cubik.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" rel="noreferrer" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:enet-discuss-request@cubik.org" target="_blank">enet-discuss-request@cubik.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:enet-discuss-owner@cubik.org" target="_blank">enet-discuss-owner@cubik.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of ENet-discuss digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Partial Reliability (Elshad Mustafayev)<br>
2. Re: Partial Reliability (Lee Salzman)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 11 Feb 2016 15:49:04 +0400<br>
From: Elshad Mustafayev <<a href="mailto:elshad@goubiq.com" target="_blank">elshad@goubiq.com</a>><br>
To: <a href="mailto:enet-discuss@cubik.org" target="_blank">enet-discuss@cubik.org</a><br>
Subject: [ENet-discuss] Partial Reliability<br>
Message-ID:<br>
<<a href="mailto:CAKR9mN83nvD3UHFtsHeku1d-kFDLbP2k2xvUyB3uoY2HFa%2BrMA@mail.gmail.com" target="_blank">CAKR9mN83nvD3UHFtsHeku1d-kFDLbP2k2xvUyB3uoY2HFa+rMA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello,<br>
<br>
We want to use enet for our project for its udp reliability. However, we<br>
are looking for partial reliability feature. In other words, instead of<br>
retransmitting the packet until it is received by the peer, attempt some<br>
number of retransmissions bounded by some maximum number and if it is still<br>
not received just ignore and continue. Is this feature available in enet?<br>
If not how can we change the source to get this feature?<br>
<br>
Thanks.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.cubik.org/pipermail/enet-discuss/attachments/20160211/7c304832/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.cubik.org/pipermail/enet-discuss/attachments/20160211/7c304832/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 11 Feb 2016 10:32:51 -0500<br>
From: Lee Salzman <<a href="mailto:lsalzman@gmail.com" target="_blank">lsalzman@gmail.com</a>><br>
To: Discussion of the ENet library <<a href="mailto:enet-discuss@cubik.org" target="_blank">enet-discuss@cubik.org</a>><br>
Subject: Re: [ENet-discuss] Partial Reliability<br>
Message-ID:<br>
<<a href="mailto:CAPk1TVHd6vUUStsEtf0XU3fheiCpXRxP-ezJodKCbg%2BqNQCyqw@mail.gmail.com" target="_blank">CAPk1TVHd6vUUStsEtf0XU3fheiCpXRxP-ezJodKCbg+qNQCyqw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Just use a normal unreliable packet and do your own retransmits/acks<br>
above that, as that stuff becomes a bit too application specific that<br>
enet does not provide it.<br>
<br>
On Thu, Feb 11, 2016 at 6:49 AM, Elshad Mustafayev <<a href="mailto:elshad@goubiq.com" target="_blank">elshad@goubiq.com</a>> wrote:<br>
> Hello,<br>
><br>
> We want to use enet for our project for its udp reliability. However, we are<br>
> looking for partial reliability feature. In other words, instead of<br>
> retransmitting the packet until it is received by the peer, attempt some<br>
> number of retransmissions bounded by some maximum number and if it is still<br>
> not received just ignore and continue. Is this feature available in enet? If<br>
> not how can we change the source to get this feature?<br>
><br>
> Thanks.<br>
><br>
> _______________________________________________<br>
> ENet-discuss mailing list<br>
> <a href="mailto:ENet-discuss@cubik.org" target="_blank">ENet-discuss@cubik.org</a><br>
> <a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" rel="noreferrer" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
><br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org" target="_blank">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" rel="noreferrer" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
<br>
<br>
------------------------------<br>
<br>
End of ENet-discuss Digest, Vol 146, Issue 1<br>
********************************************<br>
</blockquote></div><br></div>
<br>_______________________________________________<br>
ENet-discuss mailing list<br>
<a href="mailto:ENet-discuss@cubik.org">ENet-discuss@cubik.org</a><br>
<a href="http://lists.cubik.org/mailman/listinfo/enet-discuss" rel="noreferrer" target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
<br></blockquote></div><br></div>