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.

Sign up for GitHub

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

Jump to bottom

QUESTION: I noticed MavSDK initiates 4 MavlinkMessageHandler when connecting using MavSDK-JAVA. Why does MavSDK initiates 4 handlers to handle MavLink messages? Are there any reasons for this approach? #2410

Open

Ba0Nguyen opened this issue Oct 1, 2024 · 1 comment

Labels

Ba0Nguyen commented Oct 1, 2024

No description provided.

Ba0Nguyen changed the title ~~QUESTION: I noticed MavSDK initiates 4 MavlinkMessageHandler when connected using MavSDK-JAVA. Why does MavSDK initiates 4 handlers to handle MavLink messages? Are there any reasons for this approach?~~ QUESTION: I noticed MavSDK initiates 4 MavlinkMessageHandler when connecting using MavSDK-JAVA. Why does MavSDK initiates 4 handlers to handle MavLink messages? Are there any reasons for this approach?

Collaborator

julianoes commented Oct 1, 2024

How exactly did you determine that? Or what is your concern overall?

julianoes added the question label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment