feat: verify to support Cache Flush on Failure Indication #267
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 patch is to resolve issue #54 by implement a function to support Cache Flush on Failure Indication
A new API of
ServiceDaemon
is added:The idea is that, a querier can call this API anytime to verify if the service records still valid. A
ServiceRemoved
event will be triggered if no response intimeout
.DnsResource
supportsSRV
record andADDR
record at this moment.For convenience,
VERIFY_RESOURCE_TIMEOUT_DEFAULT
is defined fortimeout
.UPDATE:
I simplified the new API based on this thought: (most) users would not make 2 calls to verify
service_instance_name
andhostname
for one service instance. The user should be able to call just once to verify a service instance. The library will send query for both SRV and ADDR records internally.The API now is this: