- All Known Implementing Classes:
@ThreadSafe public interface ClientInterceptorInterface for intercepting outgoing calls before they are dispatched by a
Implementers use this mechanism to add cross-cutting behavior to
Channeland stub implementations. Common examples of such behavior include:
- Logging and monitoring call behavior
- Adding metadata for proxies to observe
- Request and response rewriting
The interceptor may be called for multiple
callsby one or more threads without completing the previous ones first. Refer to the
ClientCall.Listenerdocs for more details regarding thread safety of the returned listener.
<ReqT,RespT> ClientCall<ReqT,RespT> interceptCall(MethodDescriptor<ReqT,RespT> method, CallOptions callOptions, Channel next)Intercept
ClientCallcreation by the
Many variations of interception are possible. Complex implementations may return a wrapper around the result of
next.newCall(), whereas a simpler implementation may just modify the header metadata prior to returning the result of
next.newCall()must not be called under a different
Contextother than the current
Context. The outcome of such usage is undefined and may cause memory leak due to unbounded chain of
method- the remote method to be called.
callOptions- the runtime options to be applied to this call.
next- the channel which is being intercepted.
- the call object for the remote operation, never