You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Berlin, we discussed the ability to "ping" a display to help users disambiguate between multiple receivers (perhaps with similar names) that may show up in a list of named receivers. This would be useful in a meeting room with multiple displays, for example.
This is not currently not possible given the way the protocol is specified today, so we agreed to track this as a v2 issue. The user workflow in the time being will be to leverage the authentication UI (such as the receiver showing a pin) to verify that the receiver chosen was the correct one.
The text was updated successfully, but these errors were encountered:
scottlow
changed the title
Add ability to "ping" a display to help with discovery
Add ability to "ping" a receiver to help with discovery
May 23, 2019
In Berlin, we discussed the ability to "ping" a display to help users disambiguate between multiple receivers (perhaps with similar names) that may show up in a list of named receivers. This would be useful in a meeting room with multiple displays, for example.
This is not currently not possible given the way the protocol is specified today, so we agreed to track this as a v2 issue. The user workflow in the time being will be to leverage the authentication UI (such as the receiver showing a pin) to verify that the receiver chosen was the correct one.
The text was updated successfully, but these errors were encountered: