From: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
To: Ahmad Gani <reyuki@gnuweeb.org>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
"GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>
Subject: Re: [PATCH gwproxy v5 2/2] dnsparser: Add dns parser code
Date: Sat, 23 Aug 2025 02:09:34 +0700 [thread overview]
Message-ID: <CAOG64qO9w0A3Zo3wTDzczvPVidhMGh-hEv6P8wk4WPQSB87jGQ@mail.gmail.com> (raw)
In-Reply-To: <CAOG64qNcmXdb-e2ZS4Za1Y871xNeCNUNGhQNoaa7GS6GF=TzgQ@mail.gmail.com>
On Fri, Aug 22, 2025 at 8:48 PM Alviro Iskandar Setiawan wrote:
> On Fri, Aug 22, 2025 at 12:44 PM Ahmad Gani wrote:
> > I just pushed a new branch at my github fork of gwproxy [1], you can take
> > a look if you want in the branch refactor-dns-feature.
>
> Nice, tq. I will take a look after the Jackson Hole speech.
(( The Jackson Hole's speech was very dovish, congrats if you went long ;-) ))
So, I have taken a look into your branch. And I saw commit
a02b58fe34ed ("dns: Remove code block related to the usage of glibc's
getaddrinfo_a function"). I am a little bit worried about that part.
My suggestion would be to create a new option in the configure file to
select what resolver type to be used. Let's mark this new feature as
experimental and keep the old feature for now. If your feature has
become stable enough, we can move forward abandoning getaddrinfo_a()
entirely.
Maybe './configure --use-raw-dns-resolver' or something else to enable
your experimental feature. If you go that way, don't forget to update
the GitHub CI to test your new feature.
What do you think?
next prev parent reply other threads:[~2025-08-22 19:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 4:46 [PATCH gwproxy v5 0/2] Initial work on integration of DNS parser lib in gwproxy Ahmad Gani
2025-08-14 4:46 ` [PATCH gwproxy v5 1/2] dns: Allow only port string number Ahmad Gani
2025-08-14 7:15 ` Alviro Iskandar Setiawan
2025-08-14 4:46 ` [PATCH gwproxy v5 2/2] dnsparser: Add dns parser code Ahmad Gani
2025-08-14 7:28 ` Alviro Iskandar Setiawan
2025-08-14 7:43 ` Alviro Iskandar Setiawan
2025-08-16 16:03 ` Ammar Faizi
2025-08-16 16:30 ` Ahmad Gani
2025-08-16 16:40 ` Ammar Faizi
2025-08-21 16:50 ` Alviro Iskandar Setiawan
2025-08-22 5:43 ` Ahmad Gani
2025-08-22 13:48 ` Alviro Iskandar Setiawan
2025-08-22 19:09 ` Alviro Iskandar Setiawan [this message]
2025-08-22 19:52 ` Ammar Faizi
2025-08-23 1:07 ` Ahmad Gani
2025-08-23 1:52 ` Ammar Faizi
2025-08-23 2:17 ` Ahmad Gani
2025-08-23 2:22 ` Ammar Faizi
2025-08-23 2:20 ` Alviro Iskandar Setiawan
2025-08-23 2:28 ` Ammar Faizi
2025-08-24 13:36 ` Ahmad Gani
2025-08-25 14:37 ` Ammar Faizi
2025-08-28 0:13 ` Ammar Faizi
2025-08-28 1:51 ` Ahmad Gani
2025-08-28 2:29 ` Ahmad Gani
2025-08-28 2:45 ` Ahmad Gani
2025-08-28 2:52 ` Ahmad Gani
2025-08-28 4:19 ` Ammar Faizi
2025-08-28 4:00 ` Ammar Faizi
2025-08-16 16:41 ` (subset) [PATCH gwproxy v5 0/2] Initial work on integration of DNS parser lib in gwproxy Ammar Faizi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOG64qO9w0A3Zo3wTDzczvPVidhMGh-hEv6P8wk4WPQSB87jGQ@mail.gmail.com \
--to=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=gwml@vger.gnuweeb.org \
--cc=reyuki@gnuweeb.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox