Dude this is like production ready!
This commit is contained in:
parent
34dd074310
commit
df282ae9d8
4 changed files with 15 additions and 26 deletions
26
TODO.md
26
TODO.md
|
|
@ -5,30 +5,12 @@
|
|||
- [x] use the "update_hash" function in piece checking
|
||||
- [ ] signaling when file is done
|
||||
|
||||
- [ ]
|
||||
|
||||
- [ ] per-file stats
|
||||
- [ ] per-peer stats
|
||||
|
||||
- [ ] slow peers cause slowness in the end, need the "end of game" algorithm
|
||||
- [ ] will require implementing cancel message
|
||||
- [x] slow peers cause slowness in the end, need the "end of game" algorithm
|
||||
|
||||
someday:
|
||||
- [ ] cancellation from the client-side for the lib (i.e. stop the torrent manager)
|
||||
|
||||
|
||||
# concurrency
|
||||
it's fucked up now, so need to rethink.
|
||||
|
||||
Sequencing:
|
||||
- when the peer sends bitfield
|
||||
- update its bitfield
|
||||
- this can only happen at the start. But it can also NOT happen at all (if the peer wants to download)
|
||||
- so we actually cannot use it as a trigger to start the "uploader" of it (where we upload to it)
|
||||
- however both this and "have" we can use as a trigger to start the "downloader" part of it
|
||||
- when the peer sends "interested"
|
||||
- when the peer sends "have"
|
||||
- update its bitfield
|
||||
|
||||
"peer downloader":
|
||||
- if started, means there was some initial interest
|
||||
- if we are unchoked:
|
||||
- fetch new pieces forever from the queue, send requests
|
||||
- [ ] cancellation from the client-side for the lib (i.e. stop the torrent manager)
|
||||
Loading…
Add table
Add a link
Reference in a new issue