Add well-known handler #2
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Played around with this a bit and added a module to handle the
.well-known/libp2p/protocols
endpoint. The underlying idea is this enables other peers who discover us to understand what protocols we support and how to reach them. In a standard server/client deployment there is a lot of coordination on what protocol is where. With the well-known resource we can avoid this coordination and allow peers to learn about each other in a similar way to theidentify
protocol.Example Caddyfile Usage:
Note that the user has to explicitly advertise protocols. I think this is okay, but could be better. I'm just not very familiar with caddy. Maybe it's possible to mark other routes/handlers with a decorator.