feat: Create MatrixResolver::create_dns_resolver() #30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "zoe/add-create-dns-resolver"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Returns a
MatrixDnsResolverwhich correctly implements DNS caching for correct SNI behavior.MatrixResolver::create_dns_resolver()feat: Createto WIP: feat: CreateMatrixResolver::create_dns_resolver()MatrixResolver::create_dns_resolver()WIP: feat: Createto feat: CreateMatrixResolver::create_dns_resolver()MatrixResolver::create_dns_resolver()397294dd7fbc4e487ddeLGTM
@ -268,0 +269,4 @@////// See more details in `MatrixDnsResolver`'s doc commentpub fn create_dns_resolver(self: &Arc<Self>) -> MatrixDnsResolver {MatrixDnsResolver::new(self.resolver.clone(), self.cache.clone(), self.clone())I set up the client builder stuff with the intention that our method of SNI wouldn't be exposed, so if reqwest fixed their missing feature it wouldn't require a breaking change
I agree, but unless you wanna rewrite i think literally most of resolvematrix around this one change, this might be the easiest solution.
I also attempted to create a MatrixDnsResolver manually, but its so tightly coupled to the dns resolver, the cache, and the matrixresolver that its basically impossible
Fair. Probably a valid workaround.
Blocks continuwuation/continuwuity#1934