Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Named Networks #8

Open
monoman opened this issue May 10, 2019 · 1 comment
Open

Named Networks #8

monoman opened this issue May 10, 2019 · 1 comment
Assignees
@monoman
Labels
enhancement New feature or request

Comments

@monoman
Copy link
Contributor

monoman commented May 10, 2019 •
edited
Loading

InterlockLedger networking use the concept of Named Networks which are completely segregated: nodes reject any messages that aren't tagged with the network Id they are configured to listen. Currently this is done in the upper-level message envelope, specific to InterlockLedger implementation, but probably it should be generalized, and brought down here in the base level library.

It would help also with the Anti-DDOS effort
@monoman monoman added the enhancement New feature or request label May 10, 2019
@monoman
Copy link
Contributor Author

monoman commented Jul 3, 2019 •
edited
Loading

PeerServices instantiation now receives a Network Name, but so far only uses it for logging purposes. We need to define the Network Id format and how it is embedded in the streaming.

@monoman monoman self-assigned this May 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@monoman monoman

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@monoman