-
Notifications
You must be signed in to change notification settings - Fork 33
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
[P2P] Replace addressing via ServiceUrl/GenericParam with P2P routing #426
Comments
@deblasis Made a few edits to the description so the scope is pretty clearly defined now. |
Thank you @Olshansk 🙏 |
@jessicadaugherty and @bryanchriswhite investigate how much of this was accomplished through P2P refacotring and update or delete accordingly |
@bryanchriswhite Can you review this ticket after merging in all the ongoing work, I think it'll be either resolved or no longer relevant. |
All deliverables have been completed over the course of libp2p integration and refactoring. |
Objective
Offload the business logic of message routing entirely to the
P2P
moduleWe currently connect nodes using the endpoint (host & port) captured in an actor's
ServiceUrl
, which is retrieved/set using theGenericParam
field in the proto. See #313 for the source of this naming and grep forgeneric_param
in the codebase to find its uses. By default, we configure nodes to list on port 8080.Hosts, ports and endpoint logic/complexity should be encapsulated inside the
P2P
module. No other modules, or configurations files (e.g. geneis et al) should have any understanding of network routing other than cryptographic identities.Origin Document
If you are taking on this task, make sure to read this discussion first: #403 (comment)
Goals
P2P
moduleP2P
moduleDeliverable
TODO (#426):
in the codebaseActorToNetworkPeer
)Non-goals / Non-deliverables
GenericParam
/ActorSpecificParam
([Utility] Design & implement a better approach toGenericParam
/ActorSpecificParam
#313)General issue deliverables
Testing Methodology
make ...
make ...
make test_all
LocalNet
is still functioning correctly by following the instructions at docs/development/README.mdCreator: @deblasis
Co-Owners: @Olshansk
The text was updated successfully, but these errors were encountered: