Skip to content
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

Clarity on the use of Friendly name #330

Open
backkem opened this issue Apr 25, 2024 · 1 comment
Open

Clarity on the use of Friendly name #330

backkem opened this issue Apr 25, 2024 · 1 comment

Comments

@backkem
Copy link
Contributor

backkem commented Apr 25, 2024

The current Chromium implementation requires a friendly name as represented by a "fn" mDNS txt record.

I wanted to confirm if:

  1. Is this a remnant from google cast and a requirement we want to remove, as the OSP spec covers this by the instance name and the display name in the metadata discovery.
  2. There is still some merit to having a friendly name and we need, so we'll update the OSP spec accordingly.
@wangw-1991
Copy link
Contributor

I think the biggest difference between friendly name and instance name is that: instance name should be unique and mDNS conflict resolution procedure is used to guarantee it (in current chromuim, if an instance name is already used, a sequence number will be added to the instance name to form a new instance name), while friendly name doesn't have to be unique.

@markafoltz markafoltz added the F2F label Aug 22, 2024
@markafoltz markafoltz removed the F2F label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants