Hi,

I write an example of sending message through a utp stream: jason-ni@76b93ec

However, it can not be compiled. It seems the "Send" marker is not sufficient to allow spawning a future with UtpStream. I tried to add the "Sync" marker. Then it can be compiled and run as expected. But I don't think that's the correct fix. My simple code may not be complicated enough to trigger some race condition.

Another issue is the UtpStream is hard to be split into read half and write half like tokio's TcpStream. Splitting to 2 separated halves is critical to implement a full-duplex proxy, as I understand(tokio-rs/tokio#1108).

Maybe we need to add another layer of indirection by using channel. How do you think?

Hi,
I really love this library. I've been looking through other Rust bittorrent libraries, and none seem to work quite as well. While cargotorrent seems to be the other main rust torrenting library, I have issues running it (though I'm using a proot container in Termux, so I'd expect some issues). The only issue I have with this repo is a lack of documentation, which is to be expected from a crate in active development. If you wouldn't mind, though, even some very basic documentation on starting and stopping a torrent would be great.

Hi,

Thank you for this fantastic library! I found it yesterday and learned a lot rust techniques I didn't know. When I wrote a simple example to test the utp feature, I found that there may be a small issue of timeout handling on the SyncSent state. Below is my naive fix:

jason-ni@1d074ee

...