TimingProvider interface #7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The specification now details how a TimingObject, implemented by a user agent, may be associated with a TimingProvider object, implemented by a timing resource provider. All procedures have been updated accordingly. Several parts will probably need to be adjusted or completely updated over time but this version should already provide a solid basis to enable multi-device synchronization scenarios. The TimingProvider interface and the requirements on timing resource providers are minimal, on purpose.
ingararntzen
added a commit
that referenced
this pull request
Jul 11, 2015
TimingProvider interface. Thanks Francois. Following your suggestion this pull request is merged now, but may be subject to changes later on.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The specification now details how a
TimingObject, implemented by a user agent, may be associated with aTimingProviderobject, implemented by a timing resource provider.All procedures have been updated accordingly.
Several parts will probably need to be adjusted or completely updated but this version should already provide a solid basis to enable multi-device synchronization scenarios.
I kept the TimingProvider interface and the requirements on timing resource providers to a bare minimum, on purpose. This meant exposing a
nowmethod instead of the more complexquerymethod that would require timing resource providers to manipulate vectors. As for the rest, this is of course open to discussion!I suggest to merge this pull request and start making changes from there.