-
Notifications
You must be signed in to change notification settings - Fork 471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Ensure services indicate their dependencies through identifiers #2263
Labels
dependencies
Pull requests that update a dependency file
dx
Developer Experience
topic/dependencies
Topic dependencies
Comments
achingbrain
added a commit
that referenced
this issue
Jun 12, 2024
Allows services to optionally define the capabilities they provide to the rest of libp2p and also the capabilities they require from other services. This allows, for example, the `WebRTC` transport to require the `CircuitRelay` transport to be present, or `KAD-DHT` (or anything that uses a topology) to require the identify protocol. Fixes #2263 Refs #2135
3 tasks
achingbrain
added a commit
that referenced
this issue
Jun 12, 2024
Allows services to optionally define the capabilities they provide to the rest of libp2p and also the capabilities they require from other services. This allows, for example, the `WebRTC` transport to require the `CircuitRelay` transport to be present, or `KAD-DHT` (or anything that uses a topology) to require the identify protocol. Fixes #2263 Refs #2135
achingbrain
added a commit
that referenced
this issue
Jun 12, 2024
Allows services to optionally define the capabilities they provide to the rest of libp2p and also the capabilities they require from other services. This allows, for example, the `WebRTC` transport to require the `CircuitRelay` transport to be present, or `KAD-DHT` (or anything that uses a topology) to require the identify protocol. Fixes #2263 Refs #2135
achingbrain
added a commit
that referenced
this issue
Jun 13, 2024
Allows services to optionally define the capabilities they provide to the rest of libp2p and also the capabilities they require from other services. This allows, for example, the `WebRTC` transport to require the `CircuitRelay` transport to be present, or `KAD-DHT` (or anything that uses a topology) to require the identify protocol. Fixes #2263 Refs #2135
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dependencies
Pull requests that update a dependency file
dx
Developer Experience
topic/dependencies
Topic dependencies
As suggested in #2135 In order for services to indicate their dependencies so that consumers can utilize the libp2p stack effectively, we should have each service return a list of other services it requires, which would be verified on startup.
Related: #1762
The text was updated successfully, but these errors were encountered: