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

Message identification for logging and communication #8

Open
cptshirty opened this issue Aug 6, 2024 · 0 comments
Open

Message identification for logging and communication #8

cptshirty opened this issue Aug 6, 2024 · 0 comments

Comments

@cptshirty
Copy link

Hello, for my application I need to be able to log and eventually send messages through serial interface.
For this application it's important to be ablle to differentiate between the messages in case you write/read from a log file.
I am thinking of storing the messages like {class_id}{message_id}{the message struct}.

I am actually working on this on my fork of the project and i think it would be beneficial to merge upstream, since logging and communication is a part of a lot of projects, so I created this issue just so we can discuss this and there is a place to link the pull request if you agree that this is a good idea.

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

No branches or pull requests

1 participant