From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Compressing ELPA
Date: Wed, 03 Aug 2016 12:29:41 -0400 [thread overview]
Message-ID: <jwvtwf1es63.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 3b1b8be3-3521-8aa5-cc46-7df181e26bdb@gmail.com
>> I know in theory we could have the web server de-compress the files on
>> the fly if/when the client doesn't support compression, but somehow
>> I wasn't able to make this work
>> (http://stackoverflow.com/questions/26895894/get-apache-to-auto-decompress-a-file-but-only-if-needed).
> Couldn't you do it the other way around? That is, could the files be stored
> uncompressed on the server, and could the compression be taken care of by
> the server itself, when requests arrive?
It would be the next best thing (storing the files uncompressed is
silly), yes.
> (Isn't that the standard way to do things?)
For tarballs, I highly doubt it. It's often faster to pack and unpack
a compressed tarball than an uncompressed one (because (de)compression
is faster than disk access), so there's really no advantage to ever
manipulate an uncompressed tarball, in the usual case.
In any case, any help configugin the webserver to get something like
that would be welcome.
Stefan
next prev parent reply other threads:[~2016-08-03 16:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 21:26 GnuTLS/TLS proposals for after the release Ted Zlatanov
2016-07-06 0:32 ` John Wiegley
2016-07-06 12:21 ` Ted Zlatanov
2016-07-06 14:25 ` Ted Zlatanov
2016-07-06 17:44 ` John Wiegley
2016-07-07 8:10 ` Robert Pluim
2016-07-12 13:52 ` Ted Zlatanov
2016-07-12 22:03 ` John Wiegley
2016-07-13 14:26 ` Eli Zaretskii
2016-07-13 14:43 ` Ted Zlatanov
2016-07-20 12:04 ` Lars Ingebrigtsen
2016-07-20 12:52 ` Stefan Monnier
2016-07-20 13:00 ` Compressing ELPA (was: GnuTLS/TLS proposals for after the release) Stefan Monnier
2016-08-02 20:58 ` Compressing ELPA John Wiegley
2016-08-02 22:04 ` Rostislav Svoboda
2016-08-02 22:25 ` Robert Weiner
2016-08-03 16:08 ` Clément Pit--Claudel
2016-08-03 16:29 ` Stefan Monnier [this message]
2016-07-20 13:14 ` GnuTLS/TLS proposals for after the release Ted Zlatanov
2016-07-20 14:21 ` Paul Eggert
2016-07-25 12:48 ` Ted Zlatanov
2016-07-25 13:01 ` Ted Zlatanov
2016-07-21 14:52 ` Eli Zaretskii
2016-07-21 15:22 ` Ted Zlatanov
2016-07-21 16:00 ` Eli Zaretskii
2016-07-21 16:35 ` Ted Zlatanov
2016-07-21 17:25 ` Lars Ingebrigtsen
2016-07-21 18:46 ` Eli Zaretskii
2016-07-22 14:38 ` Ted Zlatanov
2016-07-22 15:23 ` Eli Zaretskii
2016-07-23 7:44 ` Paul Eggert
2016-07-23 7:56 ` Eli Zaretskii
2016-07-22 14:38 ` Stefan Monnier
2016-07-22 15:22 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvtwf1es63.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-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/emacs.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).