-
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
Some cleanup in secure session manager code #4296
Some cleanup in secure session manager code #4296
Conversation
Size increase report for "esp32-example-build" from cb23e0c
Full report output
|
Size increase report for "nrfconnect-example-build" from cb23e0c
Full report output
|
@@ -92,136 +92,157 @@ CHIP_ERROR SecureSessionMgr::SendMessage(NodeId peerNodeId, System::PacketBuffer | |||
CHIP_ERROR SecureSessionMgr::SendMessage(PayloadHeader & payloadHeader, NodeId peerNodeId, System::PacketBufferHandle msgBuf, |
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.
Should we call these ResendMessage?
I think there should be a difference between stuff taking headers and things that decode packet/payload headers.
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.
How about SendEncryptedMessage
? From the API perspective, it does not know the CRMP is using it for resends.
@saurabhst, @jelderton, @BroderickCarlin, do you have any comments? |
Problem
SecureSessionMgr::SendMessage()
function has grown too big in size, and needs some refactoring.Summary of Changes
mTransportMgr->SendMessage
failed, it could have leaked the retained buffer)