apple/swift-nio

ClientBootstrap.resolver is hard to use for single-use resolvers

Open

#2,434 opened on May 26, 2023

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Swift (749 forks)batch import
good first issuekind/enhancement

Repository metrics

Stars
 (8,453 stars)
PR merge metrics
 (Avg merge 9d 10h) (15 merged PRs in 30d)

Description

Some resolvers (like NIO's internal GAIResolver) are use-exactly-once objects. They work only if used once (not 0 times, not twice).

ClientBootstrap.resolver is hard to use with those objects because one might want to pass around a pre-configured ClientBootstrap and then not use it or use it multiple times.

Maybe ClientBootstrap could offer a resolverFactory method that gets invoked exactly when we actually do the resolution.

The other option would that NIO could provide a Resolver type that wraps use-once resolvers and managed their lifetime (creates a fresh one when a resolution actually happens).

Contributor guide

Research direction
Investigate the current usage of ClientBootstrap.resolver and propose a resolverFactory pattern or a wrapper Resolver type that creates a fresh resolver per resolution. Consider the NIO GAIResolver as a use once resolver example.
Tech stack
swift
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
SwiftNIO
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40