unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Felix Lechner <felix.lechner@lease-up.com>,
	"Felix Lechner via Development of GNU Guix and the GNU System
	distribution." <guix-devel@gnu.org>,
	guix-devel@gnu.org
Subject: Re: Why "update substitutes?"
Date: Sat, 26 Oct 2024 16:54:43 +0000	[thread overview]
Message-ID: <9E6ADBD4-3575-4B3C-9EA8-441BA8EFC707@tobias.gr> (raw)
In-Reply-To: <87a5er6h5l.fsf@lease-up.com>

Hi Felix,

On 25 October 2024 20:50:46 UTC, "Felix Lechner via Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> wrote:
>Would it be more efficient to check whether a particular substitute is
>available in an individual query (like DNS) and stop querying for that
>substitute after a server was found?

Doesn't this describe what Guix already does?  If not, how?

I don't understand the 'like DNS' part, though, so maybe that's where it differs.  Do you mean substitute a different protocol for HTTP?

We already use a single TCP connection per server for all narinfo queries, and nars found on one server aren't queried again.



Kind regards,

T G-R

Sent on the go.  Excuse or enjoy my brevity.


      parent reply	other threads:[~2024-10-26 16:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 20:50 Why "update substitutes?" Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-10-25 23:42 ` Attila Lendvai
2024-10-26 17:07   ` Tobias Geerinckx-Rice
2024-10-26 15:12 ` Ludovic Courtès
2024-10-26 16:54   ` Suhail Singh
2024-10-26 17:08     ` Tobias Geerinckx-Rice
2024-10-26 17:23       ` Suhail Singh
2024-10-26 17:55         ` Tobias Geerinckx-Rice
2024-10-26 16:54 ` Tobias Geerinckx-Rice [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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=9E6ADBD4-3575-4B3C-9EA8-441BA8EFC707@tobias.gr \
    --to=me@tobias.gr \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.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/guix.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).