otPlatDnssdSrvResolver struct

Stops an SRV record resolver. No action is performed if no matching resolver with the same service and callback is currently active. The @p aResolver and all its contained information (strings) are only valid during this call. The platform MUST save a copy of the information if it wants to retain the information after returning from this function.

Starts an SRV record resolver. Initiates a continuous SRV record resolver for the specified service in @p aResolver. Discovered information is reported through the `mCallback` function in @p aResolver. When the service is removed it is reported with a TTL value of zero. In this case, `mHostName` may be NULL and other result fields (such as `mPort`) should be ignored. The callback may be invoked immediately with cached information (if available) and potentially before this function returns. When cached result is used, the reported TTL value will reflect the original TTL from the last received response. Multiple resolvers can be started for the same service, provided they use different callback functions.

Stops an SRV record resolver. No action is performed if no matching resolver with the same service and callback is currently active.

Iterates over SRV resolvers. Requires `OPENTHREAD_CONFIG_MULTICAST_DNS_ENTRY_ITERATION_API_ENABLE`. On success, @p aResolver is populated with information about the next resolver. The `mCallback` field is always set to `NULL` as there may be multiple active resolvers with different callbacks. Other pointers within the `otMdnsSrvResolver` structure remain valid until the next call to any OpenThread stack's public or platform API/callback.

Starts an SRV record resolver. Initiates a continuous SRV record resolver for the specified service in @p aResolver. Discovered information should be reported through the `mCallback` function in @p aResolver. When the service is removed it is reported with a TTL value of zero. In this case, `mHostName` may be NULL and other result fields (such as `mPort`) will be ignored by the OpenThread stack. The callback may be invoked immediately with cached information (if available) and potentially before this function returns. When cached result is used, the reported TTL value should reflect the original TTL from the last received response. Multiple resolvers can be started for the same service, provided they use different callback functions. The @p aResolver and all its contained information (strings) are only valid during this call. The platform MUST save a copy of the information if it wants to retain the information after returning from this function.