Channel.
Implementers use this mechanism to add cross-cutting behavior to Channel and
stub implementations. Common examples of such behavior include:
Providing authentication credentials is better served by CallCredentials. But a ClientInterceptor could set the CallCredentials within the CallOptions.
The interceptor may be called for multiple calls by one or more threads
without completing the previous ones first. Refer to the
ClientCall. docs for more details regarding thread
safety of the returned listener.
| Modifier and Type | Method and Description |
|---|---|
| public <ReqT, RespT> ClientCall | Returns: the call object for the remote operation, nevernull.the remote method to be called. method, CallOptions the runtime options to be applied to this call. callOptions, Channel the channel which is being intercepted. next)Intercept |
| interceptCall | back to summary |
|---|---|
| public <ReqT, RespT> ClientCall Intercept Many variations of interception are possible. Complex implementations may return a wrapper
around the result of
| |