public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Noah Sanci <nsanci@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: [Bug debuginfod/27277] Describe retrieved files when verbose
Date: Wed, 22 Sep 2021 16:33:31 -0400	[thread overview]
Message-ID: <20210922203331.GC13236@redhat.com> (raw)
In-Reply-To: <9ac621fee207ef233873c40843b3d34ced9019cc.camel@klomp.org>

Hi -

> > > > That in turn would require THREE new API functions or a
> > > > stateful set_HEAD_mode_and_return_dev_null one and modifying
> > > > the three main lookup functions.

> > > Yes, it definitely is more work.
> > 
> > So, is that your suggestion?  We proceed with that sort of thing?
> 
> Yes, separate the verbose printing of http headers (which I really do
> like)

(This is now done, more or less, but noting that it is not a
machine-consumable API.)

> from providing an interface to query what needs to be done to get
> some file (is it in cache, can it be retieved from a remote server, how
> big is it?) I don't think providing raw http headers is that interface.

Well, we have gone some way into this on PR28284, on various branches
including nsanci/pr28284-webapi.  It's not complete, yet the "raw http
headers" aspect is still there, because what headers are available is
unpredictable.  But now this is made even more wordy by forking the
_find_ functions into a _describe_ triplet and all the other leftover
work elsewhere.

IMHO it's not an improvement over a single function that returns
headers associated with the lookup.  Please let's discuss this again.

- FChE


  parent reply	other threads:[~2021-09-22 20:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 18:54 Noah Sanci
2021-08-05 15:13 ` Mark Wielaard
2021-08-05 16:54   ` Frank Ch. Eigler
2021-08-06 10:04     ` Mark Wielaard
2021-08-06 18:54       ` Frank Ch. Eigler
2021-08-09  9:25         ` Mark Wielaard
2021-08-23 15:11           ` Noah Sanci
2021-08-24  8:18             ` Mark Wielaard
2021-08-27 18:38               ` Noah Sanci
2021-09-08 20:56                 ` Mark Wielaard
2021-09-10 18:22                   ` Noah Sanci
2021-09-12 19:08                     ` Mark Wielaard
2021-09-13 20:07                       ` Noah Sanci
2021-09-16 10:50                         ` Mark Wielaard
2021-09-22 20:33           ` Frank Ch. Eigler [this message]
2021-09-29 14:55             ` Mark Wielaard
2021-09-29 21:28               ` Frank Ch. Eigler
2021-10-05 14:28                 ` Mark Wielaard
2022-07-14 15:32                   ` Noah Sanci
2022-08-04 13:12                     ` Mark Wielaard
     [not found]                       ` <CAJXA7qg09YkxK-NRQ31Hem0+54Us=jYC5+1siPSbHangx=SCow@mail.gmail.com>
2022-08-08 14:35                         ` Mark Wielaard
2021-08-25 18:08 Noah Sanci
2021-09-08 15:01 ` Mark Wielaard

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=20210922203331.GC13236@redhat.com \
    --to=fche@redhat.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.org \
    --cc=nsanci@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).