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
To support metadata only requests, we implement a new method on the graphsync TLI:
// GraphExchange is a protocol that can exchange IPLD graphs based on a selectortypeGraphExchangeinterface {
// ...// RequestMetadata initiates a new GraphSync metadata request to query a remote peer for the CIDs that make up a selector query. It returns raw responses from the other peer and does not verify resultsRequestMetadata(ctx context.Context, p peer.ID, root ipld.Link, selector ipld.Node, extensions...ExtensionData) (<-chanResponseData, <-chanerror)
}
Suggested Implementation
Modify RequestManager so that when we execute a metadata request, we immediately send the to the other peer, but instead of feeding the responses into a selector verification, we simply past them back to the caller.
The text was updated successfully, but these errors were encountered:
hannahhoward
changed the title
On the requestor side, we expose a new method that simply returns a stream of metadata, skipping the verification process.
Expose RequestMetadata method on graphsync client
Mar 29, 2022
What
To support metadata only requests, we implement a new method on the graphsync TLI:
Suggested Implementation
Modify RequestManager so that when we execute a metadata request, we immediately send the to the other peer, but instead of feeding the responses into a selector verification, we simply past them back to the caller.
The text was updated successfully, but these errors were encountered: