Join GitHub today
Expose a way to implement a backoff protocol, refactor errors and other minor improvements #176
This PR exposes the
I made a couple of significant refactors:
referenced this pull request
Dec 21, 2018
Well, despite the event name choice, I don't think this is a Gstreamer specific behavior. What we are exposing is a way for the Player to control the flow of data that it receives. I expect other backends to have equivalent needs, and if they don't, we can still just signal the need of data.
Anyway, I am open to suggestions about how to implement a backoff protocol in a different way :)