- Coverage
- 20%
1 out of 5 items documented0 out of 1 items with examples - Links
-
libp2p/rust-libp2p
4619 960 151 - crates.io
- Dependencies
-
- asynchronous-codec ^0.6 normal
- futures ^0.3.1 normal
- futures-timer ^3.0.2 normal
- libp2p-core ^0.38.0 normal
- libp2p-swarm ^0.41.0 normal
- log ^0.4.1 normal
- lru ^0.8.0 normal
- prost ^0.11 normal
- prost-codec ^0.3 normal
- smallvec ^1.6.1 normal
- thiserror ^1.0 normal
- void ^1.0 normal
- async-std ^1.6.2 dev
- env_logger ^0.9 dev
- prost-build ^0.11 build
- Versions
-
- 0.45.0
- 0.44.2
- 0.44.1
- 0.44.0
- 0.43.1
- 0.43.0
- 0.42.2
- 0.42.1
- 0.42.0
- 0.41.1
- 0.41.0
- 0.40.0
- 0.39.0
- 0.38.0
- 0.37.0
- 0.36.1
- 0.36.0
- 0.35.0
- 0.34.0
- 0.33.0
- 0.32.1
- 0.32.0
- 0.31.0
- 0.31.0-rc.2
- 0.31.0-rc.1
- 0.30.0
- 0.29.0
- 0.28.0
- 0.27.0
- 0.26.0
- 0.25.0
- 0.24.0
- 0.23.0
- 0.22.0
- 0.21.0
- 0.20.0
- 0.19.2
- 0.19.1
- 0.19.0
- 0.18.0
- 0.17.0
- 0.16.0
- 0.15.0
- 0.14.0-alpha.1
- 0.13.2
- 0.13.1
- 0.13.0
- 0.12.0
- 0.11.0
- 0.10.0
- 0.9.0
- 0.8.0
- 0.7.0
- 0.6.0
- 0.5.0
- 0.4.1
- 0.4.0
- 0.3.1
- 0.3.0
- 0.2.0
- 0.1.0
- Owners
-
Implementation of the [Identify](https://github.com/libp2p/specs/blob/master/identify/README.md) protocol.
This implementation of the protocol periodically exchanges
[`Info`] messages between the peers on an established connection.
At least one identification request is sent on a newly established
connection, beyond which the behaviour does not keep connections alive.
# Important Discrepancies
- **Using Identify with other protocols** Unlike some other libp2p implementations,
rust-libp2p does not treat Identify as a core protocol. This means that other protocols cannot
rely upon the existence of Identify, and need to be manually hooked up to Identify in order to
make use of its capabilities.
# Usage
The [`Behaviour`] struct implements a [`NetworkBehaviour`](libp2p_swarm::NetworkBehaviour)
that negotiates and executes the protocol on every established connection, emitting
[`Event`]s.