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
Is your feature request related to a problem? Please describe.
Currently TO_LAB directly forwards the data received from SB onto the network socket.
But in some configurations - particularly heterogeneous environments with mixtures of different CPU types - the data from the socket is not directly representable as a "C" struct.
Describe the solution you'd like
Separate this into a separate source file, and add a hook in TO_LAB to allow the write to the socket to include an encoding step prior to sending on the network. In the default implementation it would be a pass-through as it is today.
Additional context
For example, missions may dictate that all data appear in on the interconnections in "big endian" (network) byte order, and the local CPU might be little-endian, thus it needs to be encoded/translated before being forwarded to the network. This would provide the appropriate hook to allow that to happen.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Add a separate "encode" step as part of TO_LAB output forwarding.
Initially, this is just a pass through implementation, so it matches
current behavior.
Add a separate "encode" step as part of TO_LAB output forwarding.
Initially, this is just a pass through implementation, so it matches
current behavior.
jphickey
added a commit
to jphickey/to_lab
that referenced
this issue
Nov 1, 2023
Add a separate "encode" step as part of TO_LAB output forwarding.
Initially, this is just a pass through implementation, so it matches
current behavior.
Is your feature request related to a problem? Please describe.
Currently TO_LAB directly forwards the data received from SB onto the network socket.
But in some configurations - particularly heterogeneous environments with mixtures of different CPU types - the data from the socket is not directly representable as a "C" struct.
Describe the solution you'd like
Separate this into a separate source file, and add a hook in TO_LAB to allow the write to the socket to include an encoding step prior to sending on the network. In the default implementation it would be a pass-through as it is today.
Additional context
For example, missions may dictate that all data appear in on the interconnections in "big endian" (network) byte order, and the local CPU might be little-endian, thus it needs to be encoded/translated before being forwarded to the network. This would provide the appropriate hook to allow that to happen.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: