Overview
| Artifact ID: | c92fe9eba5cd090265643af21b86e8009a4c59d4664da14db26afb2cef9dc06d |
|---|---|
| Ticket: | 316edadc2411d1b5e5597c32da432c72056ca771
Add a cache in OFDNSResolver |
| User & Date: | js on 2022-11-28 22:15:17 |
Changes
- icomment:
Actually, it probably makes more sense to add the cache in `OFDNSResolver`, as there is very little reason for any kind of DNS query to be repeated if the TTL hasn't expired yet. This cache probably makes most sense to be per-instance, even though that means there is no reuse between threads. But the added locking on every lookup is probably worse than just doing one lookup per thread.
- login: "js"
- mimetype: "text/x-markdown"
- resolution changed to: "Open"
- title changed to: "Add a cache in OFDNSResolver"