-
Notifications
You must be signed in to change notification settings - Fork 204
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
Formalize and document msg number / topic id concept #2473
Comments
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Dec 6, 2023
A topic ID is the same concept as was previously referred to as a portable message number. This just formalizes it, gives it a name, and adds some macros for easier customization of the behavior.
2 tasks
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Dec 6, 2023
A topic ID is the same concept as was previously referred to as a portable message number. This just formalizes it, gives it a name, and adds some macros for easier customization of the behavior.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Dec 7, 2023
A topic ID is the same concept as was previously referred to as a portable message number. This just formalizes it, gives it a name, and adds some macros for easier customization of the behavior.
dzbaker
added a commit
that referenced
this issue
Dec 12, 2023
Fix #2473, 2475, document and use topicid numbers for cfe
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
CFE implements a logical pattern for allocation of MsgIds on multiple CPUs:
The only issue is that this pattern is not documented, and isn't consistent across other CFS apps.
Describe the solution you'd like
Document the TopicID/MsgId assignment pattern in CFE
Formalize it in the CFE header files, such that CFS apps can easily use the same pattern
Additional context
Per discussion on 2023-12-05, it was concurred that this pattern is logical and reasonable to continue following going forward, as it hits most of the objectives users likely want/need:
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: