Fixes #123 - Added a new data-change notification module#124
Open
ted-ross wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR introduces the new feature. It does not remove all of the old custom notification calls that appear throughout the code base. That will be left for a later PR.
This PR does replace the time-based periodic processing of TLS certificates with a faster and more efficient use of the new notification utility.
Note that this feature is a prerequisite for completion of the colocated-site feature.
Note also that the new utility subsumes the Watch notification. There is no longer a need to explicitly call WatchNotify after any database transactions.