[RFC] Feat: Making mini protocol components server/client aware #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cardano mini protocol is a state machine. Server and client move throughout the state machine at the same time, but just either one of them, and in final states none of them, is supposed to send messages. This is called agency.
Agency depends on state and whether the we are on the client or the server.
In Yaci, the state has been cleverly wrapped in enums, that by design are enumeration. In order to implement the isAgency we need to enhance that method with a parameter that tells whether we are on the client or server side.
Agents will be initialised w/ the isClient property and pass it to State enumeration to properly calculate agency.
This PR represents a Request For Comments where to discuss, accept or push back about the suggested design.
The code is not complete but gives an idea on the implementation.