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 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 now method instead of the more complex query method 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.
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.