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 v4 4/6] dnslookup: Initial work for implementation of C-ares-like getaddrinfo function
Date: Thu, 14 Aug 2025 11:54:58 +0700	[thread overview]
Message-ID: <CAADvAgr5wRXiJ+cwzxaYVxNdDQHNHcGZqcSF+-2oE7nWmCv+Hw@mail.gmail.com> (raw)
In-Reply-To: <aJPKOlo7CC1JB3Ia@linux.gnuweeb.org>

Sorry for the late reply! I've been caught up reading manga [1] and kind of
slacking on the development of this feature. But I'm feeling motivated
again—Anyway, let's pick up where we left off.

So, the goal is to have an abstraction for name resolution without relying
on glibc's getaddrinfo, allowing asynchronous operation without separate,
dedicated DNS thread(s), right?

On Thu, 7 Aug 2025 04:33:46 +0700 Ammar Faizi wrote:
> Let's make a simple rule. No syscalls in the DNS library. An exception
> maybe reading /etc/hosts, but you can skip that part for now.
>
> The DNS lib should at least accept:
> - Domain name.
> - Service name (port).
> - Address families to be resolved (AF_INET or AF_INET6).
> - Received bytes from the network.
> - Pointer to recv and send buffer (including their lengths).
>
> The DNS lib should at least generate:
> - Resolved addresses in 'struct gwp_sockaddr' form.
> - Bytes to be sent to the network.

I've created `gwdns_build_query` and `gwdns_parse_query`, which should
meet those criteria, please take a look at new email threads [2].

[1]:
- https://nostarch.com/microprocessors

[2]:
- https://lore.gnuweeb.org/gwml/20250814044658.252579-1-reyuki@gnuweeb.org/

--
Ahmad Gani

  reply	other threads:[~2025-08-14  4:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06  3:57 [PATCH gwproxy v4 0/6] Initial work for DNS lookup implementation Ahmad Gani
2025-08-06  3:57 ` [PATCH gwproxy v4 1/6] dnslookup: Split common functionality and struct into net.h and net.c Ahmad Gani
2025-08-06  6:18   ` Alviro Iskandar Setiawan
2025-08-06  3:57 ` [PATCH gwproxy v4 2/6] dnslookup: Add a new parameter default_port Ahmad Gani
2025-08-06  6:20   ` Alviro Iskandar Setiawan
2025-08-06  3:57 ` [PATCH gwproxy v4 3/6] dnslookup: Allow only port string number Ahmad Gani
2025-08-06  3:57 ` [PATCH gwproxy v4 4/6] dnslookup: Initial work for implementation of C-ares-like getaddrinfo function Ahmad Gani
2025-08-06  6:40   ` Alviro Iskandar Setiawan
2025-08-06  6:51     ` Alviro Iskandar Setiawan
2025-08-06  8:43       ` Ahmad Gani
2025-08-06  8:40     ` Ahmad Gani
2025-08-06 11:09   ` Alviro Iskandar Setiawan
2025-08-06 11:20     ` Alviro Iskandar Setiawan
2025-08-06 11:39       ` Ammar Faizi
2025-08-06 12:30         ` Ahmad Gani
2025-08-06 20:54           ` Ammar Faizi
2025-08-06 12:30       ` Ahmad Gani
2025-08-06 21:33         ` Ammar Faizi
2025-08-14  4:54           ` Ahmad Gani [this message]
2025-08-06  3:57 ` [PATCH gwproxy v4 5/6] dnsparser: Transaction id creation is delegated to caller Ahmad Gani
2025-08-06  6:28   ` Alviro Iskandar Setiawan
2025-08-06 10:20     ` Ahmad Gani
2025-08-06 10:51       ` Alviro Iskandar Setiawan
2025-08-06 12:29         ` Ahmad Gani
2025-08-06  3:57 ` [PATCH gwproxy v4 6/6] dnslookup: Make gw_ares_getaddrinfo asynchronous Ahmad Gani
2025-08-06  6:22   ` Alviro Iskandar Setiawan
2025-08-06  8:42     ` Ahmad Gani
2025-08-06  7:03 ` [PATCH gwproxy v4 0/6] Initial work for DNS lookup implementation Ammar Faizi
2025-08-06  7:08 ` Ammar Faizi
2025-08-06  8:37   ` Ahmad Gani
2025-08-06  8:58     ` Ammar Faizi
2025-08-06  9:47       ` Ammar Faizi
2025-08-06 20:50         ` Ammar Faizi
2025-08-06 22:14     ` Ammar Faizi
2025-08-06  7:08 ` (subset) " 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=CAADvAgr5wRXiJ+cwzxaYVxNdDQHNHcGZqcSF+-2oE7nWmCv+Hw@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