Sektor van Skijlen

Would you be able to run it under a debugger? Unfortunately I don't have an Android platform at hand to test it... Also, do you use your own application or...

In blocking mode, the connecting function (`CUDT::startConnect`) runs a loop of sending and receiving packets necessary for the handshake. In case of cut off network it simply won't receive anything...

If this is about a digitally signed packet than it should embrace all data that are identical in the first-sent packet and retransmitted packet, and the only thing that isn't...

One more thing: in case of packet re-routing, note that there are only two possibilities: 1. Re-routing on the UDP level. In this case the packet is unchanged, and so...

Actually the current implementation (since UDT) requires `SRTO_LINGER` to pass the `struct linger` type value, not integer. We can't even change it now without breaking backward compatibility.

You can take a look at my development branch `dev-groups-external-msgsync`. As I know that the method of selecting the link can be based on various parameters, I have provided a...

Just note that we decided to put it aside because it cannot support redundancy protection. Simply, if you break one link, you'll get packet drops.

This is the branch on my own clone of the repository, not in the main repository. I don't know how "mergeable" it is now against the current code, I've not...

The problem: Currently loss statistics are shifted to the very beginning and happens before any other processing. So it simply notifies all losses seen by a jump-over. This could be...

> If the packet is received out of order, there can not be sequence discontinuity by default. The packet processing unit can only see a jump-over. It doesn't know yet...