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
In order to test interoperability with other non-Python libp2p nodes, the first spec that should be ensured is that the libp2p open connection and open stream mechanisms interoperate.
In py-libp2p, the following messaging occurs when Node A and Node B open a new connection:
A dials B
A sends its peer ID to B and B sends its peer ID to A (this is where the Identify protocol would come into place, which still needs to be implemented to support different Identify services)
A and B agree on a security transport module
A and B agree on a multiplexer
Then, when Node A opens a new stream to Node B, the following messaging occurs in py-libp2p:
A sends open stream message to B
A and B agree on a particular protocol to use for communication across that stream
All PubSub mechanisms in libp2p rely on the underlying stream communication so imo it would be best to ensure opening connections and streams to non-python nodes works before moving on to testing PubSub’s interoperability
The text was updated successfully, but these errors were encountered:
In order to test interoperability with other non-Python libp2p nodes, the first spec that should be ensured is that the libp2p open connection and open stream mechanisms interoperate.
In py-libp2p, the following messaging occurs when Node A and Node B open a new connection:
Then, when Node A opens a new stream to Node B, the following messaging occurs in py-libp2p:
All PubSub mechanisms in libp2p rely on the underlying stream communication so imo it would be best to ensure opening connections and streams to non-python nodes works before moving on to testing PubSub’s interoperability
The text was updated successfully, but these errors were encountered: