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
One thing I don't see covered in ipfs/go-bitswap#543 or ipfs/specs#270 is how we actually pass an auth token to a bitswap want from the standpoint of the library consumer.
The first sounds simpler, but is quite limited. I think we need to figure out the granularity of scope we support for passing tokens. Should our mapping be simply token per session? Token per GetBlock/GetBlocks requests? Token per peer that may send us the block? Any combination thereof?
For reference: a go-data-transfer integration will be easiest if we support per-peer, but that's also the hardest to implement :(
The text was updated successfully, but these errors were encountered:
One thing I don't see covered in ipfs/go-bitswap#543 or ipfs/specs#270 is how we actually pass an auth token to a bitswap want from the standpoint of the library consumer.
I can see a couple mechanisms:
The first sounds simpler, but is quite limited. I think we need to figure out the granularity of scope we support for passing tokens. Should our mapping be simply token per session? Token per GetBlock/GetBlocks requests? Token per peer that may send us the block? Any combination thereof?
For reference: a go-data-transfer integration will be easiest if we support per-peer, but that's also the hardest to implement :(
The text was updated successfully, but these errors were encountered: