Replies: 4 comments 18 replies
-
@pacrob , @luca and @paschal533 : Wish to share that I was reviewing the multiplexer development by zig-libp2p team, who are also engineering yamux at this juncture. They have organized the project from an interop perspective: please visit zen-eth/zig-libp2p#10 Further, they have 3 sub-issues: @paschal533 and @luca: You might find this organization of sub-modules useful from a maintainability perspective. Wish to share about it. |
Beta Was this translation helpful? Give feedback.
-
Hi @acul71, about the Noise protocol question, I get where you're coming from. I added it as the primary security option because I think it's the right direction for us. I studied Rust-libp2p to implement Yamux. Rust-libp2p uses Noise as its primary security transport, with SecIO maintained for legacy compatibility. For py-libp2p, Noise is the recommended choice due to its modern design, interoperability, performance, and alignment with the libp2p ecosystem's future. This is the reason why I used Noise for Py-libp2p Yamux. I apologies for not keeping you in sync. I thought Noise has already been implemented in Py-libp2p. However since you have started working on Noise integration, I think we should take it up as a side quest later :) |
Beta Was this translation helpful? Give feedback.
-
Hi @acul71 and @seetadev, I wrote this test for switching from one stream_muxer to another (Yamux and Mplex)
Which required me to modify the test/conftest.py file a bit, From this:
To This:
And that's what is causing the conflict on the PR. This change is neccesary for the Meanwhile, I want to change the tests/conftest.py file back to this:
to resolve the conflict first, however |
Beta Was this translation helpful? Give feedback.
-
@paschal533 : Thank you for sharing. Could you please discuss with @acul71 today. We have fully replace asyncio with trio. So, having its support available within yamux and mplex is necessary. Please touch base with @pacrob for his suggestions and feedback too. We received his guidance and support on using trio in important py-libp2p PRs. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
@luca and @paschal533 : Great work and wonderful contribution. Please continue research and development discussion on yamux + mplex at this web page.
Kindly keep the PR page for code commits and refinement. Appreciate your great initiative and progress.
Beta Was this translation helpful? Give feedback.
All reactions