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
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
//! The application logic of a DNS server.
//!
//! The [`Service::call`] function defines how the service should respond to a
//! given DNS request. resulting in a future that yields a stream of one or
//! more future DNS responses, and/or [`ServiceFeedback`].
use Display;
use Deref;
use Duration;
use crateRcode;
use crate;
use crate;
use crateStreamTarget;
use Request;
//------------ Service -------------------------------------------------------
/// The type of item that `Service` implementations stream as output.
pub type ServiceResult<Target> = ;
/// `Service`s are responsible for determining how to respond to DNS requests.
///
/// For an overview of how services fit into the total flow of request and
/// response handling see the [`net::server`] module documentation.
///
/// Each `Service` implementation defines a [`call`] function which takes a
/// [`Request`] DNS request as input and returns a future that yields a stream
/// of one or more items each of which is either a [`CallResult`] or
/// [`ServiceError`].
///
/// Most DNS requests result in a single response, with the exception of AXFR
/// and IXFR requests which can result in a stream of responses.
///
/// # Usage
///
/// You can either implement the [`Service`] trait on a struct or use the
/// helper function [`service_fn`] to turn a function into a [`Service`].
///
/// # Implementing the `Service` trait on a `struct`
///
/// ```
/// use core::future::ready;
/// use core::future::Ready;
/// use core::pin::Pin;
///
/// use std::task::{Context, Poll};
///
/// use futures_util::stream::{once, Once, Stream};
///
/// use domain::base::iana::{Class, Rcode};
/// use domain::base::message_builder::AdditionalBuilder;
/// use domain::base::{Name, Message, MessageBuilder, StreamTarget};
/// use domain::net::server::message::Request;
/// use domain::net::server::service::{CallResult, Service, ServiceResult};
/// use domain::net::server::util::mk_builder_for_target;
/// use domain::rdata::A;
///
/// fn mk_answer(
/// msg: &Request<Vec<u8>, ()>,
/// builder: MessageBuilder<StreamTarget<Vec<u8>>>,
/// ) -> AdditionalBuilder<StreamTarget<Vec<u8>>> {
/// let mut answer = builder
/// .start_answer(msg.message(), Rcode::NOERROR)
/// .unwrap();
/// answer.push((
/// Name::root_ref(),
/// Class::IN,
/// 86400,
/// A::from_octets(192, 0, 2, 1),
/// )).unwrap();
/// answer.additional()
/// }
///
/// fn mk_response_stream(msg: &Request<Vec<u8>, ()>)
/// -> Once<Ready<ServiceResult<Vec<u8>>>>
/// {
/// let builder = mk_builder_for_target();
/// let additional = mk_answer(msg, builder);
/// let item = Ok(CallResult::new(additional));
/// once(ready(item))
/// }
///
/// //------------ A synchronous service example ------------------------------
/// struct MySyncService;
///
/// impl Service<Vec<u8>, ()> for MySyncService {
/// type Target = Vec<u8>;
/// type Stream = Once<Ready<ServiceResult<Self::Target>>>;
/// type Future = Ready<Self::Stream>;
///
/// fn call(
/// &self,
/// msg: Request<Vec<u8>, ()>,
/// ) -> Self::Future {
/// ready(mk_response_stream(&msg))
/// }
/// }
///
/// //------------ An anonymous async block service example -------------------
/// struct MyAsyncBlockService;
///
/// impl Service<Vec<u8>, ()> for MyAsyncBlockService {
/// type Target = Vec<u8>;
/// type Stream = Once<Ready<ServiceResult<Self::Target>>>;
/// type Future = Pin<Box<dyn std::future::Future<Output = Self::Stream> + Send>>;
///
/// fn call(
/// &self,
/// msg: Request<Vec<u8>, ()>,
/// ) -> Self::Future {
/// Box::pin(async move { mk_response_stream(&msg) })
/// }
/// }
///
/// //------------ A named Future service example -----------------------------
/// struct MyFut(Request<Vec<u8>, ()>);
///
/// impl std::future::Future for MyFut {
/// type Output = Once<Ready<ServiceResult<Vec<u8>>>>;
///
/// fn poll(self: Pin<&mut Self>, cx: &mut Context<'_>) -> Poll<Self::Output> {
/// Poll::Ready(mk_response_stream(&self.0))
/// }
/// }
///
/// struct MyNamedFutureService;
///
/// impl Service<Vec<u8>, ()> for MyNamedFutureService {
/// type Target = Vec<u8>;
/// type Stream = Once<Ready<ServiceResult<Self::Target>>>;
/// type Future = MyFut;
///
/// fn call(&self, msg: Request<Vec<u8>, ()>) -> Self::Future { MyFut(msg) }
/// }
/// ```
///
/// The above are minimalist examples to illustrate what you need to do, but
/// lacking any actual useful behaviour. They also only demonstrate returning
/// a response stream containing a single immediately available value via
/// `futures_util::stream::Once` and `std::future::Ready`.
///
/// In your own [`Service`] impl you would implement actual business logic
/// returning single or multiple responses synchronously or asynchronously as
/// needed.
///
/// # Advanced usage
///
/// The [`Service`] trait takes two generic types which in most cases you
/// don't need to specify as the defaults will be fine.
///
/// For more advanced cases you may need to override these defaults.
///
/// - `RequestMeta`: Use this to pass additional custom data to your service.
/// [Middleware] services use this to pass data to the next layer.
///
/// - `RequestOctets`: By specifying your own `RequestOctets` type you can use
/// a type other than `Vec<u8>` to transport request bytes through your
/// application.
///
/// [`DgramServer`]: crate::net::server::dgram::DgramServer
/// [`StreamServer`]: crate::net::server::stream::StreamServer
/// [middleware]: crate::net::server::middleware
/// [`net::server`]: crate::net::server
/// [`call`]: Self::call()
/// [`service_fn`]: crate::net::server::util::service_fn()
//--- impl Service for Deref
/// Helper trait impl to treat a [`Deref<Target = impl Service>`] as a [`Service`].
//------------ ServiceError --------------------------------------------------
/// An error reported by a `Service`.
//--- Display and Error
//--- From<PushError>
//--- From<ParseError>
//------------ ServiceFeedback -----------------------------------------------
/// Feedback from a `Service` to a server asking it to do something.
//------------ CallResult ----------------------------------------------------
/// The result of processing a DNS request via [`Service::call`].
///
/// Directions to a server on how to respond to a request.
///
/// In most cases a [`CallResult`] will be a DNS response message.
///
/// If needed a [`CallResult`] can instead, or additionally, contain a
/// [`ServiceFeedback`] directing the server or connection handler handling
/// the request to adjust its own configuration, or even to terminate the
/// connection.
//--- From<AdditionalBuilder>
//--- From<ServiceFeedback>