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

Draft: Add a special class for network receiver and sender reactors #190

Merged
merged 7 commits into from
Jul 18, 2023

Conversation

byeonggiljun
Copy link
Collaborator

@byeonggiljun byeonggiljun commented Jul 12, 2023

This PR adds a special class for the federated execution as network actions are managed by each network reactor, not the top-level federated reactor. The name of the class is NetworkReactor instead of FederatedReactor because they are not federated and are used for processing network actions.

NetworkSender reactors are registerd to an array of NetworkReactors.
NetworkSender reactros does not require a port ID, so make it optional
parameter.
Output control reactions are registered to a set of reactions. It is
executed by the function `_iterationComplete`.
The level of each reaction should be checked before do that reaction.
However, it cannot be achieved if we execute output control reactions at
the end of the logical tag. Thus, I made the reactionQ as 'protected' to
push output control reactions into it. It is safe because only the
App and FederatedApp can access that Q.
@byeonggiljun byeonggiljun linked an issue Jul 16, 2023 that may be closed by this pull request
@byeonggiljun byeonggiljun linked an issue Jul 16, 2023 that may be closed by this pull request
@byeonggiljun byeonggiljun merged commit b65400d into ts-level-assignment Jul 18, 2023
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

Successfully merging this pull request may close these issues.

1 participant