public inbox for gwml@vger.gnuweeb.org
 help / color / mirror / Atom feed
From: reyuki <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 v1 0/3] Initial work for DNS lookup implementation
Date: Tue, 5 Aug 2025 13:28:13 +0700	[thread overview]
Message-ID: <CAADvAgrPcRCcoVUids6iMhTnm5s=RqwAU3+ssRm0GV=8+bN5+w@mail.gmail.com> (raw)
In-Reply-To: <aIwkO9Aw+IFht0vd@biznet-home.integral.gnuweeb.org>

On Fri, Aug 1, 2025 at 9:19 AM Ammar Faizi wrote:
> The socks5 lib can do that. Why the DNS lib not?

In the case of the SOCKS5 lib, it focuses on parsing, and all network-related
tasks are handled directly by the caller. That’s why I was a bit confused
at first.

But wait—I think I’ve figured it out. I got an idea, I just need some time
to think it through. Thanks for helping me think through the problem.

I can make the DNS lib behave similarly. Instead of delegating the tasks
directly, I can provide an interface that helps the caller handle the
socket-related work.

Sorry for the late reply—I’ve been feeling a bit out of control lately.
My mind keeps telling me to finish this as fast as possible, but when I don’t
understand something, I get easily frustrated and end up watching anime
to distract myself, instead of calmly working through the problem.

I really need to fix that mindset.

Anyway, just give me a moment—I’ll send the patches shortly.

--
Ahmad Gani

      reply	other threads:[~2025-08-05  6:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31  3:07 [PATCH gwproxy v1 0/3] Initial work for DNS lookup implementation Ahmad Gani
2025-07-31  3:07 ` [PATCH gwproxy v1 1/3] dnslookup: split common functionality and struct into net.c Ahmad Gani
2025-07-31 14:01   ` Ammar Faizi
2025-07-31 18:28     ` Alviro Iskandar Setiawan
2025-07-31 18:36       ` Ammar Faizi
2025-07-31 18:42         ` Alviro Iskandar Setiawan
2025-07-31 18:53           ` Ammar Faizi
2025-07-31 19:03             ` Alviro Iskandar Setiawan
2025-07-31  3:07 ` [PATCH gwproxy v1 2/3] dnslookup: Allow only port string number Ahmad Gani
2025-07-31  3:07 ` [PATCH gwproxy v1 3/3] dnslookup: Initial work for implementation of C-ares-like getaddrinfo function Ahmad Gani
2025-07-31 18:19   ` Alviro Iskandar Setiawan
2025-07-31 19:14   ` Alviro Iskandar Setiawan
2025-08-01  1:51     ` reyuki
2025-08-01 23:32       ` Alviro Iskandar Setiawan
2025-07-31 13:39 ` [PATCH gwproxy v1 0/3] Initial work for DNS lookup implementation Ammar Faizi
2025-08-01  1:49   ` reyuki
2025-08-01  2:19     ` Ammar Faizi
2025-08-05  6:28       ` reyuki [this message]

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='CAADvAgrPcRCcoVUids6iMhTnm5s=RqwAU3+ssRm0GV=8+bN5+w@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