unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 47431@debbugs.gnu.org
Subject: bug#47431: Process Whois connection broken by remote peer.
Date: Mon, 29 Mar 2021 22:16:26 +0800	[thread overview]
Message-ID: <CAGP6POJxqrEDyqhAXJkU7Awxhjvf1PMP8sr-vDNqmDoKGwH4VQ@mail.gmail.com> (raw)
In-Reply-To: <a83bd81e9adbc578797f@heytings.org>

On Mon, Mar 29, 2021 at 8:12 PM Gregory Heytings <gregory@heytings.org> wrote:
>
>
> >>>> Possibly with a cache to mitigate the above problem.
> >>>
> >>> I'd wait with caching until we see a performance problem.  It isn't
> >>> like people are expected to invoke this command many times in a row.
> >>
> >> I think you misunderstood what I meant.  The idea would be to cache the
> >> replies from the whois.iana.org server, not those of the final whois
> >> server.  IOW, the idea would be to dynamically build a local database
> >> instead of relying on a hard-coded list.
> >
> > I understand that, and I'm still questioning the need for such a cache.
> >
> > If you have a cache, you need to manage it: add items that aren't there,
> > delete items no longer pertinent, etc.  Emacs sessions can run for many
> > moons, so the cache will have to be dynamically adjusted.
> >
>
> Yes, I know this.
>
> >
> > By contrast, requesting the list each time a query is invoked is much
> > easier, so if performance is reasonable, why bother with a cache and
> > risk subtle issues?
> >
>
> It's not a performance issue, it's a privacy issue.  Emacs users might not
> want to communicate all their queries to two servers when communicating
> them to a single server is possible.
>
> It might also (but that's not yet clear) be an abuse issue, as Lars
> pointed out.  It's not clear whether the whois.iana.org server is intended
> to be repeatedly queried by whois clients.

AFAICS, there should be the following considerations:

1. The whois.iana.org should not be queried by each of the clients on
the world repeated for each query which may overload the server.
2. Every whois query should be sent directly to a server near the
client's geographic location.

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Polytechnic University of Science and Technology engineering
NO. 552 North Gangtie Road, Xingtai, China





  reply	other threads:[~2021-03-29 14:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27  1:39 bug#47431: Process Whois connection broken by remote peer Hongyi Zhao
2021-03-27  6:30 ` Eli Zaretskii
2021-03-27  7:23   ` Gregory Heytings
2021-03-27  8:08     ` Eli Zaretskii
2021-03-27 11:01       ` Gregory Heytings
2021-03-27 11:04         ` Gregory Heytings
2021-03-28 15:39         ` Lars Ingebrigtsen
2021-03-28 20:23           ` Gregory Heytings
2021-03-29  0:19             ` Hongyi Zhao
2021-03-29  4:50             ` Eli Zaretskii
2021-03-29  7:35               ` Gregory Heytings
2021-03-29  8:38                 ` Eli Zaretskii
2021-03-29 11:31                   ` Gregory Heytings
2021-03-29 12:02                     ` Eli Zaretskii
2021-03-29 12:12                       ` Gregory Heytings
2021-03-29 14:16                         ` Hongyi Zhao [this message]
2021-03-29 10:58             ` Lars Ingebrigtsen
2021-03-29 11:20               ` Gregory Heytings
2021-03-29 12:19                 ` Gregory Heytings
2021-03-30 13:22                   ` Lars Ingebrigtsen
2021-03-31  7:53                     ` Gregory Heytings
2021-03-31 13:39                       ` Lars Ingebrigtsen
2021-03-31 14:27                         ` Gregory Heytings
2021-04-14 14:55                           ` Stefan Kangas
2022-06-28 13:40                           ` Lars Ingebrigtsen
2022-07-28 10:35                             ` Lars Ingebrigtsen
2022-07-28 21:56                               ` Gregory Heytings
2022-07-29 11:34                                 ` Lars Ingebrigtsen
2021-03-27  9:50   ` Hongyi Zhao
2021-03-27  9:57   ` Hongyi Zhao
2021-03-27 10:33     ` Eli Zaretskii
2021-03-27 12:29       ` Hongyi Zhao
2021-03-27 13:44         ` Eli Zaretskii
2021-03-28  1:41           ` Hongyi Zhao
2021-03-28  6:38             ` Eli Zaretskii
2021-03-28  7:12               ` Hongyi Zhao
2021-03-28 14:11                 ` Lars Ingebrigtsen
2021-03-28 14:15                   ` Eli Zaretskii
2021-03-28 14:19                     ` Lars Ingebrigtsen
2021-03-28 14:55                       ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGP6POJxqrEDyqhAXJkU7Awxhjvf1PMP8sr-vDNqmDoKGwH4VQ@mail.gmail.com \
    --to=hongyi.zhao@gmail.com \
    --cc=47431@debbugs.gnu.org \
    --cc=gregory@heytings.org \
    --cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).