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
When a consumer uses Waku.dial() to dial a peer, the function internally directly calls libp2p.dialProtocol(), and with the change in #2192 (comment), as a proxy but still directly calls libp2p.dial() -- this is fine until we want to tailor this connection to Waku's connection management:
A simple feature like Keep Alive Management is ignored in this process, along with lesser important but nice-to-have features like dial management (retries, backoffs), and connection tagging based on discovery method.
Expected Behavior
Any, and all, dials should have as much metadata along with crucial feature support like keep alive management a part of them
The text was updated successfully, but these errors were encountered:
weboko
changed the title
feat: external dials via Waku.dial() should have crucial feature support
feat: enable redial on fails for Waku.dial()Jan 28, 2025
Description
When a consumer uses
Waku.dial()
to dial a peer, the function internally directly callslibp2p.dialProtocol()
, and with the change in #2192 (comment), as a proxy but still directly callslibp2p.dial()
-- this is fine until we want to tailor this connection to Waku's connection management:A simple feature like Keep Alive Management is ignored in this process, along with lesser important but nice-to-have features like dial management (retries, backoffs), and connection tagging based on discovery method.
Expected Behavior
Any, and all, dials should have as much metadata along with crucial feature support like keep alive management a part of them
The text was updated successfully, but these errors were encountered: