You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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: