feat: Use socom for inter daemon communication#141
Draft
mariuswbr wants to merge 87 commits into
Draft
Conversation
Transport socom semantics over IPC to another process. It uses shared memory for payloads to avoid copying huge payloads.
massif did not work yet but I am on it
However some changes should be considered workarounds
The Error type does not own any string, only string_view. Thus it the error message given must be likely a static string
send() can fail whenever the peer disconnects
Tests never reach the body and IMHO it checks for illegal state
|
The created documentation from the pull request is available at: docu-html |
… times from multiple threads
db31a4e to
50d250b
Compare
…t shared memory configuration for method calls and event updates.
50d250b to
3aca0bb
Compare
This file contains hidden or 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.
No description provided.