From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#47431: Process Whois connection broken by remote peer. Date: Mon, 29 Mar 2021 12:12:27 +0000 Message-ID: References: <835z1dp0qg.fsf@gnu.org> <83y2e9nhne.fsf@gnu.org> <87zgynp9t5.fsf@gnus.org> <406246af7fb57420287b@heytings.org> <83k0pqmulc.fsf@gnu.org> <83a6qmmk11.fsf@gnu.org> <831rbymal3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24083"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, 47431@debbugs.gnu.org, hongyi.zhao@gmail.com To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Mar 29 14:13:21 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lQqll-0006BU-Sw for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 29 Mar 2021 14:13:21 +0200 Original-Received: from localhost ([::1]:47368 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lQqlk-0000Ax-TV for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 29 Mar 2021 08:13:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60592) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lQqlT-0000AC-A4 for bug-gnu-emacs@gnu.org; Mon, 29 Mar 2021 08:13:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36483) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lQqlS-0003Mk-H0 for bug-gnu-emacs@gnu.org; Mon, 29 Mar 2021 08:13:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lQqlS-0004xy-9d for bug-gnu-emacs@gnu.org; Mon, 29 Mar 2021 08:13:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 29 Mar 2021 12:13:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47431 X-GNU-PR-Package: emacs Original-Received: via spool by 47431-submit@debbugs.gnu.org id=B47431.161701995119038 (code B ref 47431); Mon, 29 Mar 2021 12:13:02 +0000 Original-Received: (at 47431) by debbugs.gnu.org; 29 Mar 2021 12:12:31 +0000 Original-Received: from localhost ([127.0.0.1]:48029 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lQqkx-0004x0-BX for submit@debbugs.gnu.org; Mon, 29 Mar 2021 08:12:31 -0400 Original-Received: from heytings.org ([95.142.160.155]:45990) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lQqkv-0004wr-80 for 47431@debbugs.gnu.org; Mon, 29 Mar 2021 08:12:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20210101; t=1617019947; bh=jAueWPUXaXMUBEwNY2t2K2Dt2hgDp+qeyRmsTNWWzxU=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=emJa2sHNkHk/yAeYawuV4CsURjLCH7lXhkujUxo8+pGcgadnLOyo+EpyIKH0hwjTS Vf+85QW+5jPc8tlvFGDiOMQAa4dwQtNlVVh5nCiC3T20X+EhERJ1+lVjl4SqOkYh9b +3mSFVgwsx6+0cHRH0mPfNNa/Dv3yRfB+FCIujRsnGtJlnTaMi3a+J93qcgukgFSD0 QH5eTJNExG1XmZXt/BW0XYXzRIY/G/sISb7rWXLynZDVHdloo7ciyorlW2s+iCI0/9 qW2u2oMVuZ7cWrzAHeYgp44B96eoiN6GX+YbEi2FEUS00eo8KOgZX10eyeLsPHHerf 0SHwyKIuZ99Qg== In-Reply-To: <831rbymal3.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:203235 Archived-At: >>>> 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.