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.

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

Routing: With or Without Target #3

Open
decanus opened this issue Aug 29, 2019 · 0 comments
Open

Routing: With or Without Target #3

decanus opened this issue Aug 29, 2019 · 0 comments

Comments

@decanus
Copy link
Contributor

decanus commented Aug 29, 2019

Problem

Due to the fact that our MANET is supposed to handle various different scenarios we also have different routing requirements, for example in a chat context messages should be routed to a specific target as fast as possible. However when we are broadcasting ethereum transactions a flooding type system may be perfectly legitimate.

Solution

Allow for various routing methodologies that can messages can either be sent to a specific target, service provider or broadcasted within the network. This should also affect metering, messages that affect less nodes should cause less to be "metered".

Acceptance criteria

Nodes are able to receive messages in various means, being sent them directly or receiving them through broadcasts. Nodes should also provide "static" identifiers in order for messages to be able to be forwarded to them directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant