Allow access to Components/Registrar from DialOptions/ListenerOptions when creating a new transport

[ckousik]

When creating a new transport, we are unable to register any new streams with the registrar, or fetch handles for any incoming streams. We are also unable to find the list of supported protocols, incoming and outgoing stream limits, and track metrics. Currently, transport implementations implement the MultiaddrConnection interface and use the upgrader for muxing, encryption, and handling streams. This is unnecessary when using transports which inherently contain encryption and stream multiplexing (WebRTC, QUIC). Allowing access to the components or some subset of it containing the registrar would simplify implementing these transports.

[achingbrain]

If your transport implements Initializable it'll get handed a Components instance after construction - that'll give you access to the Registrar and other libp2p components.

At that point you should be able to do stream/connection gating, encryption, multiplexing, etc in the same way the upgrader does for transports that don't have their own versions of these things.

Hopefully that helps?

[ckousik]

Yes, thank you! We can close this issue.