-
Notifications
You must be signed in to change notification settings - Fork 109
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
Multiple protocol support #35
Labels
Comments
aregtech
added
enhancement
New feature or request
help wanted
Extra attention is needed
labels
Nov 3, 2021
aregtech
changed the title
Channel and serialization refactoring, prepare multiple protocol support
Multiple protocol support
Nov 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Goal
AREG SDK should support multiple protocols to be able to communicate with various networks and devices.
Motivation
The industry is using various networks and protocols for their use. In order to be easier integrated in different networks and communicate with other devices, or seamlessly to integrate in existing solutions, AREG SDK should support multiple protocols to serialize and de-serialize data.
Background information
Each protocols means a separate network / connection, which means separate channel. Analyze and consider the possibility of serialization / deserialization in the channel. The component may use multiple channels for the communication. Depending on the channel instance, provide serialization mechanism. This as well means that the channel is responsible to instantiate an event object, which contains message buffer with the serialized data.
Remark: This feature requires some restructuring and refactoring. At this very moment the refactoring is not the highest priority. This ticket as well has multiple dependencies like multi-channel (issue #31), optimization of the event and the optimization of message creation. (issue #66).
The text was updated successfully, but these errors were encountered: