You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to be able to listen to an event on the core and for each peer in core.peers to find out when a bitfield is updated. The end goal for this would be to create diffs of the bitfield changes. For example, this event might provide something like the values used in Peer.onbitfield & Peer.onrange.
The text was updated successfully, but these errors were encountered:
@mafintosh any further thoughts on whether this is possible / practical?
Use case: know what data / size of data that needs to be uploaded to / downloaded from a particular peer, ultimately to know whether replication has "finished" e.g. all data that can be sent has been sent, and all data that can be received can be received. But also to provide a user feedback on progress of replication and an estimation of time to completion.
It would be useful to be able to listen to an event on the core and for each peer in
core.peers
to find out when a bitfield is updated. The end goal for this would be to create diffs of the bitfield changes. For example, this event might provide something like the values used in Peer.onbitfield & Peer.onrange.The text was updated successfully, but these errors were encountered: