forked from grpc/grpc-swift
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathClientInterceptor.swift
110 lines (109 loc) · 4.25 KB
/
ClientInterceptor.swift
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
/*
* Copyright 2023, gRPC Authors All rights reserved.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
/// A type that intercepts requests and response for clients.
///
/// Interceptors allow you to inspect and modify requests and responses. Requests are intercepted
/// before they are handed to a transport and responses are intercepted after they have been
/// received from the transport. They are typically used for cross-cutting concerns like injecting
/// metadata, validating messages, logging additional data, and tracing.
///
/// Interceptors are registered with the server via ``ClientInterceptorPipelineOperation``s.
/// You may register them for all services registered with a server, for RPCs directed to specific services, or
/// for RPCs directed to specific methods. If you need to modify the behavior of an interceptor on a
/// per-RPC basis in more detail, then you can use the ``ClientContext/descriptor`` to determine
/// which RPC is being called and conditionalise behavior accordingly.
///
/// - TODO: Update example and documentation to show how to register an interceptor.
///
/// Some examples of simple interceptors follow.
///
/// ## Metadata injection
///
/// A common use-case for client interceptors is injecting metadata into a request.
///
/// ```swift
/// struct MetadataInjectingClientInterceptor: ClientInterceptor {
/// let key: String
/// let fetchMetadata: @Sendable () async -> String
///
/// func intercept<Input: Sendable, Output: Sendable>(
/// request: StreamingClientRequest<Input>,
/// context: ClientContext,
/// next: @Sendable (
/// _ request: StreamingClientRequest<Input>,
/// _ context: ClientContext
/// ) async throws -> StreamingClientResponse<Output>
/// ) async throws -> StreamingClientResponse<Output> {
/// // Fetch the metadata value and attach it.
/// let value = await self.fetchMetadata()
/// var request = request
/// request.metadata[self.key] = value
///
/// // Forward the request to the next interceptor.
/// return try await next(request, context)
/// }
/// }
/// ```
///
/// Interceptors can also be used to print information about RPCs.
///
/// ## Logging interceptor
///
/// ```swift
/// struct LoggingClientInterceptor: ClientInterceptor {
/// func intercept<Input: Sendable, Output: Sendable>(
/// request: StreamingClientRequest<Input>,
/// context: ClientContext,
/// next: @Sendable (
/// _ request: StreamingClientRequest<Input>,
/// _ context: ClientContext
/// ) async throws -> StreamingClientResponse<Output>
/// ) async throws -> StreamingClientResponse<Output> {
/// print("Invoking method '\(context.descriptor)'")
/// let response = try await next(request, context)
///
/// switch response.accepted {
/// case .success:
/// print("Server accepted RPC for processing")
/// case .failure(let error):
/// print("Server rejected RPC with error '\(error)'")
/// }
///
/// return response
/// }
/// }
/// ```
///
/// For server-side interceptors see ``ServerInterceptor``.
public protocol ClientInterceptor: Sendable {
/// Intercept a request object.
///
/// - Parameters:
/// - request: The request object.
/// - context: Additional context about the request, including a descriptor
/// of the method being called.
/// - next: A closure to invoke to hand off the request and context to the next
/// interceptor in the chain.
/// - Returns: A response object.
func intercept<Input: Sendable, Output: Sendable>(
request: StreamingClientRequest<Input>,
context: ClientContext,
next: (
_ request: StreamingClientRequest<Input>,
_ context: ClientContext
) async throws -> StreamingClientResponse<Output>
) async throws -> StreamingClientResponse<Output>
}