dirkmc
dirkmc
The do not send CIDs list is used in the case where a data transfer must be restarted because the connection goes down. When the connection comes back up, the...
> Would your solution then be to first pull all the key-values and then use the links as root CIDs for subsequent transfers? That's how I would imagine it working,...
The data systems team probably has more insight than I do but I think you're right that you'd want to build an abstraction on top of the data transfer module....
I agree that we should improve the UX for outputing the state of the transfer. As I understand it the current behaviour is: 1. Graphsync client requests data Transfer moves...
I agree that it's nice for the caller to have feedback on the state of their request. I suggest we think about it in terms of the trade-off between keeping...
Agree with changing the naming, I think it's confusing at the moment 👍
Will I think for paid retrieval the client kind of has to know how big the thing they're downloading is, otherwise they don't know if they can afford to download...
> One thing I'm genuinely planning of here is that the payment layer lives out of process. I'm in favour of this idea 👍 It should help enable different payment...
If we fail to even open the channel, the expected behaviour is that it will fail the transfer immediately (it doesn't try to restart) Once the channel is open (once...
When go-data-transfer receives a block, it adds the CID to a list. If the data transfer is restarted, eg because the connection went down, the receiving side sends a list...