416-MemoryLane / issue-tracking

0 stars 0 forks source link

Finalize Protocol for Message Handling #21

Closed eysk-io closed 1 year ago

eysk-io commented 1 year ago

With the validation of all of the components of our application (https://github.com/416-MemoryLane/issue-tracking/issues/1, https://github.com/416-MemoryLane/issue-tracking/issues/4, https://github.com/416-MemoryLane/issue-tracking/issues/7, https://github.com/416-MemoryLane/issue-tracking/issues/11), we can finalize the message-handling protocol.

eysk-io commented 1 year ago

The protocol specified here is assuming that Galactus is operating as expected and nodes are unreachable only temporarily: https://docs.google.com/document/d/14vIT3723LqF5FTqVwAjJ-wtqnfSGWYKn2jReFrXMdqA/edit?usp=sharing

There should be a separate protocol that works in conjunction with the protocol specified here to handle nodes going offline.