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
Currently, when an offer comes in, the content key is checked on whether it is inRange and next whether it is not yet in our db.
If both are true, content transfer is accepted. If there are more offers of the same content before it gets transferred, validated & stored in the db, these will also be initiated.
We should cache the content key or content id and verify if no offer/accept is already ongoing for the same content.
One important side node, if the ongoing transfer fails or the content is not valid for some reason, a RFC should be launched for that content so that node can still receive it from another node.
The text was updated successfully, but these errors were encountered:
Currently, when an offer comes in, the content key is checked on whether it is
inRange
and next whether it is not yet in our db.If both are true, content transfer is accepted. If there are more offers of the same content before it gets transferred, validated & stored in the db, these will also be initiated.
We should cache the content key or content id and verify if no offer/accept is already ongoing for the same content.
One important side node, if the ongoing transfer fails or the content is not valid for some reason, a RFC should be launched for that content so that node can still receive it from another node.
The text was updated successfully, but these errors were encountered: