Lines Matching refs:to

19 new one if necessary.  It also has to listen for responses from the
22 responses to `DnsTlsTransport`.
29 responses to `DnsTlsTransport` (through the `IDnsTlsObserver` interface).  It doesn't
30 know anything about which queries correspond to which responses, and does not retain
31 state to indicate whether there is an outstanding query.
38 Classes that spawn a helper thread call `thread::join()` in their destructor to ensure
42 annotations) to minimize the likelihood of a latent threading bug.  The unit tests are
43 also heavily threaded to exercise this functionality.
52 The query method writes a struct (containing a pointer to the query) to the pipe
58 We need to pass messages between threads using a pipe, and not a condition variable
59 or a thread-safe queue, because the socket thread has to be blocked
60 in `poll()` waiting for data from the server, but also has to be woken
62 threads have to arrive on a socket, so that `poll()` can listen for them.
64 to read and write in OpenSSL](https://www.openssl.org/blog/blog/2017/02/21/threads/)).
70 query a new ID for transmission, records the mapping from input IDs to sent IDs, and
71 applies the inverse mapping to responses before returning them to the caller.
76 `DnsTlsQueryMap` will scan the ID space to find an available ID, or fail the query
77 if there are no available IDs.  Queries will not block waiting for an ID number to
88 to 3 times before reporting failure to `DnsTlsDispatcher`.
89 This limit helps to ensure proper functioning in the case of a recursive resolver that
90 is malfunctioning or is flooded with requests that are stalled due to malfunctioning
98 increases latency on the first query after an idle period, but also helps to avoid
103 reuse sessions more than once, it should not be possible to hit this limit.
114 For unit testing, we would like to be able to mock out `DnsTlsSocket`.  This is
123 run without actually connecting over TLS to a test server.  (The integration tests