rust-libp2p/protocols/relay/src/multiaddr_ext.rs

use libp2p_core::multiaddr::Protocol;
use libp2p_core::Multiaddr;

pub(crate) trait MultiaddrExt {
    fn is_relayed(&self) -> bool;
}

impl MultiaddrExt for Multiaddr {
    fn is_relayed(&self) -> bool {
        self.iter().any(|p| p == Protocol::P2pCircuit)
    }
}
feat(swarm)!: allow `NetworkBehaviour`s to manage connections Previously, a `ConnectionHandler` was immediately requested from the `NetworkBehaviour` as soon as a new dial was initiated or a new incoming connection accepted. With this patch, we delay the creation of the handler until the connection is actually established and fully upgraded, i.e authenticated and multiplexed. As a consequence, `NetworkBehaviour::new_handler` is now deprecated in favor of a new set of callbacks: - `NetworkBehaviour::handle_pending_inbound_connection` - `NetworkBehaviour::handle_pending_outbound_connection` - `NetworkBehaviour::handle_established_inbound_connection` - `NetworkBehaviour::handle_established_outbound_connection` All callbacks are fallible, allowing the `NetworkBehaviour` to abort the connection either immediately or after it is fully established. All callbacks also receive a `ConnectionId` parameter which uniquely identifies the connection. For example, in case a `NetworkBehaviour` issues a dial via `NetworkBehaviourAction::Dial`, it can unambiguously detect this dial in these lifecycle callbacks via the `ConnectionId`. Finally, `NetworkBehaviour::handle_pending_outbound_connection` also replaces `NetworkBehaviour::addresses_of_peer` by allowing the behaviour to return more addresses to be used for the dial. Resolves #2824. Pull-Request: #3254. 2023-02-24 10:43:33 +11:00			`use libp2p_core::multiaddr::Protocol;`
			`use libp2p_core::Multiaddr;`

			`pub(crate) trait MultiaddrExt {`
			`fn is_relayed(&self) -> bool;`
			`}`

			`impl MultiaddrExt for Multiaddr {`
			`fn is_relayed(&self) -> bool {`
			`self.iter().any(\|p\| p == Protocol::P2pCircuit)`
			`}`
			`}`