You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should also be done for _matterc._udp (not only _matter._tcp). May I suggest to call SetCacheFlush(true) directly in SrvResponder::AddAllResponses and TxtResponder::AddAllResponses so that it becomes impossible to forget setting this flag. Apple's mDNSResponder and avahi sets this flag for SRV and TXT entries for service registrations.
The instance name is randomly generated and should thus be unique, so the cache-flush bit should be set. The main benefit of this is that it allows an optimization for mDNS clients such that they do not have to send a new query if it already has a cached entry (typically from the "Additional Records" section from a previous PTR query). From RFC 6762:
An additional efficiency optimization SHOULD be performed when a
Multicast DNS response is received containing a unique answer (as
indicated by the cache-flush bit being set, described in Section 10.2, "Announcements to Flush Outdated Cache Entries"). In this
case, there is no need for the querier to continue issuing a stream
of queries with exponentially increasing intervals, since the receipt
of a unique answer is a good indication that no other answers will be
forthcoming.
The text was updated successfully, but these errors were encountered:
Follow up for #23918 and #23933 (comment).
This should also be done for _matterc._udp (not only _matter._tcp). May I suggest to call
SetCacheFlush(true)
directly inSrvResponder::AddAllResponses
andTxtResponder::AddAllResponses
so that it becomes impossible to forget setting this flag. Apple's mDNSResponder and avahi sets this flag for SRV and TXT entries for service registrations.The instance name is randomly generated and should thus be unique, so the cache-flush bit should be set. The main benefit of this is that it allows an optimization for mDNS clients such that they do not have to send a new query if it already has a cached entry (typically from the "Additional Records" section from a previous PTR query). From RFC 6762:
The text was updated successfully, but these errors were encountered: