public inbox for gwml@vger.gnuweeb.org
 help / color / mirror / Atom feed
From: Ahmad Gani <reyuki@gnuweeb.org>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Alviro Iskandar Setiawan <alviro.iskandar@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 08:07:08 +0700	[thread overview]
Message-ID: <CAADvAgo0jW44FtZ5D-epwuHzUmW7qTXmR=OgNWZhx7Y7+KVMBA@mail.gmail.com> (raw)
In-Reply-To: <20250822195242.GA3236201-ammarfaizi2@gnuweeb.org>

On Sat, Aug 23, 2025 at 2:52 AM Ammar Faizi <ammarfaizi2@gnuweeb.org> wrote:
> On Sat, Aug 23, 2025 at 02:09:34AM +0700, Alviro Iskandar Setiawan wrote:
> > (( The Jackson Hole's speech was very dovish, congrats if you went long ;-) ))
>
> Lol. No need to bring the portofolio discussion to this thread. Ahmad
> won't care about it anyway.

Yeah, I might be interested if I were rich and have a truckload of money :-)

> > 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.
>
> Agree with your idea. The same with io_uring feature in gwproxy. I
> assume the io_uring feature is still experimental and it is not enabled
> by default. We will probably never delete epoll code, forever. But the
> old DNS code may be deleted later if this one goes well.

I think it should be fine to have old DNS code removed if the raw DNS
resolver feature is only applied when it's completed and tested.

You can still keep the old DNS feature in the master branch that is meant
to be stable (?)

--
Ahmad Gani

  reply	other threads:[~2025-08-23  1:07 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
2025-08-22 19:52               ` Ammar Faizi
2025-08-23  1:07                 ` Ahmad Gani [this message]
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='CAADvAgo0jW44FtZ5D-epwuHzUmW7qTXmR=OgNWZhx7Y7+KVMBA@mail.gmail.com' \
    --to=reyuki@gnuweeb.org \
    --cc=alviro.iskandar@gnuweeb.org \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=gwml@vger.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