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

Add hooks for encoding/translating of network buffer #167

Closed
jphickey opened this issue Oct 25, 2023 · 0 comments · Fixed by #168
Closed

Add hooks for encoding/translating of network buffer #167

jphickey opened this issue Oct 25, 2023 · 0 comments · Fixed by #168
Assignees

Comments

@jphickey
Copy link
Contributor

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.

@jphickey jphickey self-assigned this Oct 25, 2023
jphickey added a commit to jphickey/to_lab that referenced this issue Oct 27, 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.
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.
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.
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 a pull request may close this issue.

1 participant