Resume on failure

The main reason I cannot use sharedrop, is because it does not resume where it left off after a failure. When the computer goes to sleep, or the connection drops, the sender should ask the receiver how many bytes the receiver got, and resume sending from there.

@szimek Any update on this?

Unfortunately, I don't have much time to work on it, but resuming on failure and optimizing transfer speeds are the first things I'll work on when I have some free time.

I was thinking about using webtorrent for handling file transfers - as it uses bittorrent protocol, it should be much easier to handle failures, but it's probably a lot of work to switch to it.

You can try out webtorrent yourself at https://instant.io - maybe it will be better for you till I manage to fix this issue in ShareDrop.

@szimek wow thanks for the links!