unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Pierre Neidhardt <mail@ambrevar.xyz>, 34807@debbugs.gnu.org
Subject: [bug#34807] [PATCH 1/2] Add (guix lzlib).
Date: Tue, 07 May 2019 01:28:09 +0200	[thread overview]
Message-ID: <87v9ynf9iu.fsf@nckx> (raw)
In-Reply-To: <87a7fzffip.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

Ludo',

Ludovic Courtès wrote:
> So, depending on the client, ‘guix publish’ should return either 
> a
> narinfo-for-gzip or a narinfo-for-lzip.  To make it possible, 
> new
> clients could send an extra HTTP header, say 
> ‘X-Guix-Compression’, that
> would specify their preferred compression method(s).  ‘guix 
> publish’
> would take that into account when replying.

There's a standard[0] HTTP header for that: ‘Accept-Encoding’.

Unfortunately (and for reasons that I cannot fathom), it doesn't 
use standard MIME types, but pseudostandard strings like ‘gzip’ 
and ‘br’.  We can boldly add ‘lzip’ to that :-)

Similarly, servers can send ‘Content-Encoding’[1] HTTP headers, 
but I don't see a need for it here.

Kind regards,

T G-R

[0]: 
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Encoding
[1]: 
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2019-05-06 23:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 18:02 [bug#34807] [PATCH 1/2] Add (guix lzlib) Pierre Neidhardt
2019-03-10 18:09 ` [bug#34807] [PATCH 2/2] dir-locals.el: Add 'call-with-lzip-input-port' and 'call-with-lzip-output-port' keywords Pierre Neidhardt
2019-03-22 21:35 ` [bug#34807] [PATCH 1/2] Add (guix lzlib) Ludovic Courtès
2019-05-01 16:46   ` Pierre Neidhardt
2019-05-02  9:16     ` Pierre Neidhardt
2019-05-04  9:11       ` Ludovic Courtès
2019-05-04 10:23         ` Pierre Neidhardt
2019-05-04 21:09           ` Ludovic Courtès
2019-05-04 21:39             ` Pierre Neidhardt
2019-05-06 21:18               ` Ludovic Courtès
2019-05-06 23:28                 ` Tobias Geerinckx-Rice [this message]
2019-05-07  7:02                   ` Pierre Neidhardt
2019-05-07 15:44                     ` bug#34807: " Ludovic Courtès
2019-05-07 15:51                       ` [bug#34807] " Pierre Neidhardt
2019-05-07  8:19                   ` Ludovic Courtès

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=87v9ynf9iu.fsf@nckx \
    --to=me@tobias.gr \
    --cc=34807@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).