public inbox for gwml@vger.gnuweeb.org
 help / color / mirror / Atom feed
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
Cc: Ahmad Gani <reyuki@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 09:28:47 +0700	[thread overview]
Message-ID: <20250823022847.GC3508499-ammarfaizi2@gnuweeb.org> (raw)
In-Reply-To: <CAOG64qP7EgsuqcWbWETKSOe6V2_z0M2Ap7uyrvASfyzY+43QGg@mail.gmail.com>

On Sat, Aug 23, 2025 at 09:20:17AM +0700, Alviro Iskandar Setiawan wrote:
> I think the UDP 53 resolver can be merged earlier, then later you add
> /etc/hosts support, and other missing bits after that.

Yes, let's only do that "UDP 53 resolver" first for the initial work.

Ahmad, I'll apply your patch series if your DNS resolver is already
usable from at least the epoll event loop.

io_uring support can be later, but you must not break it if you enable
your new experimental feature.

Your objective now is only focus on resolving DNS via UDP port 53. Make
it usable from the epoll event loop.

Next work will be parsing these files:

  - /etc/hosts
  - /etc/resolv.conf
  - /etc/gai.conf

and probably more files. We don't need to wait those files to be parsed
by your feature to merge it.

-- 
Ammar Faizi


  reply	other threads:[~2025-08-23  2:28 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
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 [this message]
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=20250823022847.GC3508499-ammarfaizi2@gnuweeb.org \
    --to=ammarfaizi2@gnuweeb.org \
    --cc=alviro.iskandar@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