Enables the timer scheduler's customization for both deadline and waitable timers #25
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.
This pull request is linked to pull request discussion #24
The discussion on timer precisions with @haegele-tv lead us to think that we have to design our own timer mechanism for the boost asio udt implementation requirements.
The perfect place to do so would be to design a specific timer scheduler (as it is done with WinRT, or Linux, Windows...) and benefit of the entire deadline/waitable timer io_objects and io_services architecture.
Yet, the timer scheduler is NOT customizable by the user. This patch allows third party developers to specify a custom timer scheduler for any specific requirements.
What do you think?