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

Remote playback device capabilities not always a subset of local playback device's #88

Closed
anssiko opened this issue Jun 12, 2017 · 2 comments
Labels

Comments

@anssiko
Copy link
Member

anssiko commented Jun 12, 2017

#41 (comment):

The remote playback device capabilities might not be always a subset of those of the local playback device. The cases when something is not working locally but can work remotely might be worth looking into and adding a note about too.

Should research and document such capabilities to see how to best reflect that in the spec.

@anssiko
Copy link
Member Author

anssiko commented Oct 24, 2017

There are two classes of interoperability issues discussed in #41:

  • a feature X is not working locally, but can work remotely
  • a feature X is not working remotely, but can work locally

This issue is about the former. The issue #41 is (mainly) about the latter.

The text we put in place for the purposes of the CR publication in the Status of This Document captures the broader interoperability issue, but I still see merit in being explicit in these two classes of issues, since the solutions to them are likely different.

Let's discuss the possible solutions to the "not working locally, but can work remotely" issue in here.

@markafoltz markafoltz added the F2F label Nov 2, 2017
@mounirlamouri
Copy link
Member

Closing issue per TPAC F2F resolution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants