-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Separate Rendezvous message handling from BLE session #2418
Separate Rendezvous message handling from BLE session #2418
Conversation
With this change, BLE handling remains in RendezvousSession and message processing independent of BLE moves to RendervousMessageHandler.
const size_t bufferLen = buffer->DataLength(); | ||
char * key = nullptr; | ||
char * ssid = nullptr; | ||
char msg[bufferLen]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes the stack utilisation dependent on the received DataLength. Is the data length known to be capped to a threshold? We could be more deterministic by having the high threshold value in here?
I understand this mostly just moves the existing code into another function, maybe a follow-on then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch; I'm surprised we don't use -Wvla.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please file a followup issue to use -Wvla
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pan-apple Could you take a look, please? |
tag: @vivien-apple |
@saurabhst @BroderickCarlin @andy31415 could you take a look? |
With this change, BLE handling remains in RendezvousSession and
message processing independent of BLE moves to RendervousMessageHandler.