Add HTTPMetrics to unary interceptors
#109
Merged
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.
Adds the ability for interceptors to receive metrics data via a new closure. This is helpful for tracing, i.e., when building an interceptor that:
Ideally, this information would be included in the response callback itself (i.e., within the
HTTPResponse), butURLSessiondoes not provideURLSessionTaskMetricsat the same time that it provides the response. Furthermore, metrics tend to arrive after the response completes, and blocking the response from being passed back to the caller while waiting for metrics does not make sense. Instead, a new callback is being added to unary interceptors.Example:
Which prints something like this: