-
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
Respect updated DNS SD broadcast names in TV app #25355
Conversation
6643b86
to
e808d61
Compare
PR #25355: Size comparison from e807d2d to e808d61 Full report (1 build for cc32xx)
|
e808d61
to
70c8576
Compare
PR #25355: Size comparison from 11c2f5b to 70c8576 Decreases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
PR #25355: Size comparison from f62853e to fdfdeb5 Decreases (1 build for cc32xx)
Full report (3 builds for cc32xx, qpg)
|
PR #25355: Size comparison from 3889a44 to bd5e3eb Decreases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
PR #25355: Size comparison from ab87102 to 13517a7 Decreases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
PR #25355: Size comparison from 6bb8917 to 875d5d8 Increases (1 build for qpg)
Decreases (1 build for cc32xx)
Full report (5 builds for cc32xx, linux, qpg)
|
examples/tv-casting-app/android/App/app/src/main/jni/com/chip/casting/DiscoveredNodeData.java
Outdated
Show resolved
Hide resolved
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.
Checkmark for the purposes of updating a sample app with changes and checkmarks from app owner - I have not deeply checked the logic and without a review for 1 week this probably qualifies for fast track.
Had a comment about oddness of having a hash/equals that only considers partial class data (and I can understand usage in the array adapter ... but it is odd/unexpected that if (contains) { remove(); } add
is not actually a noop but rather replaces same;fkey data).
leaving up to app maintainer to decide what to do with it, I am giving the checkmark in advance.
Thanks! - To clarify the behavior, it does the contains to check if it is "effectively" equal, but in actual use there are some elements that might change on a new broadcast update (such as the broadcast name), and in those cases i still want the button updated. |
PR #25355: Size comparison from 43d45ef to 203dd6f Increases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
examples/tv-casting-app/android/App/app/src/main/jni/com/chip/casting/TvCastingApp.java
Show resolved
Hide resolved
…casting/TvCastingApp.java
PR #25355: Size comparison from 43d45ef to 5cd98c4 Increases (6 builds for cc13x2_26x2, cyw30739, psoc6, qpg)
Decreases (9 builds for bl602, bl702, cc13x2_26x2, mbed, psoc6)
Full report (23 builds for bl602, bl702, cc13x2_26x2, cyw30739, linux, mbed, psoc6, qpg)
|
This clarifies that the objects are "effectively equal" rather than truly equal.
PR #25355: Size comparison from 43d45ef to f83e33c Full report (1 build for cc32xx)
|
* Respect updated DNS SD broadcast names When a device is advertising over dns-sd and the TX bits change (device name) a message is sent out to indicate that the old adverisment should be expired and the new one should be used. In the current implementation of the casting app, we stop listening to updates after the `discoveryDurationSeconds` timeout. This causes us to miss messages and Android seems to fall back to the cached value of the DNS advertisment. We need to change the usage pattern here so that clients stop the discovery manually after it is started and keep it active for the lifetime they need it for. I also updated the test apps to behave a bit nicer with discovered commissioners.
* Respect updated DNS SD broadcast names When a device is advertising over dns-sd and the TX bits change (device name) a message is sent out to indicate that the old adverisment should be expired and the new one should be used. In the current implementation of the casting app, we stop listening to updates after the `discoveryDurationSeconds` timeout. This causes us to miss messages and Android seems to fall back to the cached value of the DNS advertisment. We need to change the usage pattern here so that clients stop the discovery manually after it is started and keep it active for the lifetime they need it for. I also updated the test apps to behave a bit nicer with discovered commissioners.
When a device is advertising over dns-sd and the TX bits change (device name) a message is sent out to indicate that the old advertisement should be expired and the new one should be used.
In the current implementation of the casting app, we stop listening to updates after the
discoveryDurationSeconds
timeout. This causes us to miss messages and Android seems to fall back to the cached value of the DNS advertisement.We need to change the usage pattern here so that clients stop the discovery manually after it is started and keep it active for the lifetime they need it for.
I also updated the test apps to behave a bit nicer with discovered commissioners.
Fixes #25492