Ricardo Martins

Hi, thanks for you contribution! Help me understand the rationale for this PR: what are the use cases you have in mind? I personally never feel the need to run...

2 seems to me to be the most invasive approach, while 3 feels viscerally wrong. I quickly built a prototype of 1 and a simple concurrent client (`examples/concurrent-reads-and-writes`), in the...

> The only thing, theoretically, missing for me is CloneableSocket into() trait support for UtpStream. Hm, that will require either an `UtpCloneableStream` or creating a `Socket` trait.

As it should, of course. What I'm considering is that it might be undesirable to force the user to pay the cost of using a `Mutex` even when one isn't...

Some preliminary benchmarks show that `UtpCloneableSocket` is a bit faster than a regular `UtpSocket`, which is mildly surprising. I guess the mutex isn't as terrible as I expected.

It should be fixed on e7d6cdb. > The other thing we need is to detect ungraceful connection close. Either a heartbeat, or a timeout since last packet received would work....

It has been available as an unstable feature for a while. Unfortunately we can't depend on it because the library must be compatible with stable rust. The ability to set...

Well, this is awkward. I also have a branch to handle the timeout cases I mentioned in #8, with commits I held back from that merge for further tests and...

Thank you for understanding. :) You are correct in your analysis that the congestion timeout is a retry timeout. According to the LEDBAT specification, this timeout doubles every time it...

@ned14 My schedule is not entirely rigid, except for the meetings with my thesis adviser and deadlines related to paper submissions. The deadline for submitting the thesis is late September,...