On 14 Jul 2025, at 00:08, Greg Stein <gst...@gmail.com> wrote: >> I think it depends a bit on how much this would change the API in APR. >> >> It feels like a good idea to add this to APR, since it might be useful for >> other projects as well. >> > > The *original* vision for APR was "portable runtime". Deal with the things > that were different across platforms. Haul those differences into a uniform > API. > > At some point, that got corrupted into "grab bag of utility APIs that have > nothing to do with portability" (think: database and LDAP APIs)
In the APR1 series this wasn't true. APR was the portable runtime, APR-util was the "portable bigger things". Certainly the combination of APR and APR-util into APR2 made no sense for the reasons you describe above, but here we are. > Using c-ares or unbound, as a configuration option makes more sense, and > means that we don't have to bounce our dependencies to a recent APR. ... > should the APR community want to build this in, then that could be a third > option for an async DNS resolver (c-ares, unbound, apr). Definite +1 to this. While it would be nice that APR-util supported this, it definitely shouldn't stop anyone writing code. Regards, Graham --
