Add network abstraction layer to reactor-c #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This RFC proposes adding network interoperability to the federated execution in
reactor-c, including network security and the integration of various network stacks, by introducing a network interface layer. This abstraction will facilitate the addition of other network stacks without modifying the Lingua Franca protocol or message formats. The current reactor-c code is tightly coupled with TCP sockets, making it difficult to introduce different network stacks and security features without significant changes. This proposal aims to support various communication protocols and encryption methods, such as TCP, Pub-Sub (e.g., MQTT), and SSL/TLS or Secure Swarm Toolkit (SST).The work-in-progress PRs are here: lf-lang/reactor-c#330, lf-lang/lingua-franca#2256.