public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28284] support description functionality through HEAD
Date: Thu, 20 Jan 2022 00:17:45 +0000	[thread overview]
Message-ID: <bug-28284-10460-AAndAoJTE1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28284-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28284

--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
The problem of federation reminded me that we haven't solved this problem yet.

> int debuginfod_info_debuginfo (debuginfod_client *client,
>                                const unsigned char *build_id,
>                                int build_id_len,
>                                size_t *size, size_t *transfer_size);

It'd also need the other current X-DEBUGINFOD-* response headers, -FILE: and
-ARCHIVE:.  And we'd need two other functions for source and executable.  And
if any fields get added at the server by our software (or someone else's
proxy!), the API would have to expand to match.

For federation purposes, we'd need to forward all these headers from upstream
to downstream.  And we'd like to get this data for an active transfer, not
really a historical one (don't want to have to save/cache), and not make an
extra query to a debuginfod server just to fetch this.

These considerations lead me back to suggesting an API oriented toward fetching
the headers of the current/last fetch made with a debuginfod_client, just like
the debuginfod_get_url(), returning some subset of what's currently stored by
the client code as ->winning_headers.  Specifically, I'd say save & return
those response headers with prefix "x-debuginfod-".

These ones would be the same ones that a hypothetical "debuginfod-find -d"
(describe?) option would want to print to stderr: a more concentrated output
than the -v (verbose) firehose we were talking about earlier.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-01-20  0:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 19:02 [Bug debuginfod/28284] New: " nsanci at redhat dot com
2021-08-27 19:02 ` [Bug debuginfod/28284] " nsanci at redhat dot com
2021-08-27 19:05 ` fche at redhat dot com
2021-11-10 14:17 ` mark at klomp dot org
2022-01-20  0:17 ` fche at redhat dot com [this message]
2022-05-16 18:55 ` nsanci at redhat dot com
2022-08-11 12:50 ` fche at redhat dot com
2022-08-12  9:05 ` mliska at suse dot cz
2022-09-07 23:16 ` fche at redhat dot com

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=bug-28284-10460-AAndAoJTE1@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).