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

Intelligent route discovery for messages #15

Open
ewan-carree opened this issue Jun 28, 2022 · 0 comments
Open

Intelligent route discovery for messages #15

ewan-carree opened this issue Jun 28, 2022 · 0 comments

Comments

@ewan-carree
Copy link
Member

ewan-carree commented Jun 28, 2022

Description

As a Shoset user,

When my Shoset needs to send a message to another one

I want that my Shoset takes the most optimal route

And that there is no Shoset down on this route

so that my Shoset does not have to flood the network with the same message.

Acceptance Criteria

Scenario A Shoset need to send a message to another one
Given A Shoset and no established route
When This Shoset is going to send a message to the other one
Then It must run an intelligent routing protocol to establish the route
And Use this route to send the message
Scenario A shoset from the route is down
Given A Shoset and no established route
When This Shoset is going to send a message to the other one
And There is a Shoset down on the shortest path
Then The routing protocol must automatically re-do the routing
And It must establish a new route and overwrite the old one

Constraints

  • Create intelligent routing protocol that follow these criteria:

    • The route must be the shortest path
    • If there is a Shoset down on the path, the route must be recalculated and overwrite the old one.
  • Routing must be done with logical name for each layer of the route.

@ewan-carree ewan-carree changed the title Intelligent router for messages Intelligent route discovery for messages Jun 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants