Refactoring DnsCache and how to resolve Service Instance #108
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.
Simplify the logic of resolving an instance: always resolve from the cache. For any incoming updates, we update the cache first, then try to resolve according to the cache.
We're still not doing all the things for the cache updates as mentioned in RFCs, but I think with the changes, the future enhancements will be easier.
instances_found
and the related state. As they are essentially another kind of cache but it is error-prone to keep them up-to-date and consistent withDnsCache
.