public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@sebabeach.org>
To: phil@jaj.com
Cc: overseers@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: large web pages
Date: Wed, 11 Jun 2003 18:19:00 -0000	[thread overview]
Message-ID: <20030611182149.F19C7B536@mail.sebabeach.org> (raw)
In-Reply-To: <20030611180048.GA19841@disaster.jaj.com> (message from Phil Edwards on Wed, 11 Jun 2003 14:00:48 -0400)

   Date: Wed, 11 Jun 2003 14:00:48 -0400
   From: Phil Edwards <phil@jaj.com>

   I have no clue either, but I will mention that a certain directory tree
   on the webserver is gzip'd nightly.  If the browser indicates that it can
   handle gzip'd files, that's what the server sends.  The original copy is
   also kept, for the sake of less capable browsers.

   For the life of me I can't recall which directory tree it is.  I think
   it's everything that shows up under http://gcc.gnu.org/onlinedocs/.

Jason pointed me at /www/sourceware/htdocs/gdb/onlinedocs,
and I happened to notice .gz files there.

frv-1-insn.html compresses very nicely, 1277408 -> 84001.  woohoo.
With a fast connection and a fast machine there's no significant
difference to page loading speed though.
People with slow connections would presumably notice of course.

  reply	other threads:[~2003-06-11 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11  8:05 Doug Evans
2003-06-11 12:42 ` Ben Elliston
2003-06-11 15:51   ` Doug Evans
2003-06-11 16:36     ` Doug Evans
     [not found] ` <3EE74E11.1040700@redhat.com>
2003-06-11 17:23   ` frv suggestions Doug Evans
2003-06-11 18:00 ` large web pages Phil Edwards
2003-06-11 18:19   ` Doug Evans [this message]
2003-06-12  6:13   ` Jason Molenda

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=20030611182149.F19C7B536@mail.sebabeach.org \
    --to=dje@sebabeach.org \
    --cc=cgen@sources.redhat.com \
    --cc=overseers@sources.redhat.com \
    --cc=phil@jaj.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).