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
If we are successful in building out the graphsync metadata requests, in order to ship it, we need to make it backward compatbile.
Suggested Implementation
I am inclined to defer to Libp2p versioning, even though I think it makes sense to wrap messages in a 2_1 header, wrather than try to do versioning with wrappers.
The actions to take are:
If I make a metadata only request to a peer, and in connecting we find out they only support 2.0 requests, just error.
You really don't need to do anything on the responder side, as it should only get 2.1 requests from 2.1 peers.
For all other types of requests, just downgrade to a 2.0 message if the peer only supports 2.0
I think that's it.
The text was updated successfully, but these errors were encountered:
hannahhoward
changed the title
Build backward compatibility for the 2.1 protocol when we are ready to ship
Backward compatibility for graphsync 2.1 protocol
Mar 30, 2022
Goals
If we are successful in building out the graphsync metadata requests, in order to ship it, we need to make it backward compatbile.
Suggested Implementation
I am inclined to defer to Libp2p versioning, even though I think it makes sense to wrap messages in a 2_1 header, wrather than try to do versioning with wrappers.
The actions to take are:
The text was updated successfully, but these errors were encountered: