-
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
Mark event paths as urgent when doing node-wide subscriptions in Matter.framework. #23226
Mark event paths as urgent when doing node-wide subscriptions in Matter.framework. #23226
Conversation
…er.framework. Otherwise we will not receive events until the max-interval elapses.
PR #23226: Size comparison from 9f08fc1 to 5179625 Increases (7 builds for bl602, bl702, esp32, psoc6, telink)
Decreases (4 builds for bl702, cc13x2_26x2, esp32, telink)
Full report (38 builds for bl602, bl702, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
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 this setting not be controlled in an API argument?
Is this normal behaviour? Always needing to "urgent subscribe" for wildcard events feels odd.
For these APIs, "no", because they can't change their arguments at this point. We may add other APIs later that allow control over this. This is just restoring the behavior of these APIs from before the SDK default behavior changed under them, as far as I can tell.
It's the behavior that ended up getting specced and implemented.... I don't think it's a very good behavior, but it's what we ended up with. |
Otherwise we will not receive events until the max-interval elapses.