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

Should we have a key for visibility of the player of a player being backgrounded? #137

Open
PCaponetti opened this issue Aug 22, 2024 · 0 comments

Comments

@PCaponetti
Copy link
Collaborator

In conversations about player state the state of being backgrounded and/or not visible came up. Should we have signal for this?

Options discussed so far:

  • another state in the player state key: this would mean it is mutually exclusive with other keys and only reported on state-interval mode which misses out on value to request mode where dynamic prioritization of requests can be done
  • a separate key to report in any mode: we do get the ability to prioritize requests here, but it will break with the paradigm of request and response mode tying the data to the point in time the request was sent instead of data about the segment being requested. It also leads to incomplete data as transitions to and from backgrounded mode can/will happen in between segment requests.
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

1 participant