From: Ben Elliston <bje@wasabisystems.com>
To: cgen@sources.redhat.com
Subject: Re: large web pages
Date: Wed, 11 Jun 2003 12:42:00 -0000 [thread overview]
Message-ID: <873cigiyh5.fsf@sashimi.wasabisystems.com> (raw)
In-Reply-To: <20030611080838.A848BB536@mail.sebabeach.org>
Doug Evans <dje@sebabeach.org> writes:
> To what extent should I be concerned with overtaxing sources'
> resources [sic] with large web pages? I haven't a clue what the
> threshold is before I should be concerned. Suggestions?
They might be a little big (for various values of "big"), but they
will be almost never accessed, so I don't see a problem. If you're
really concerned, ask overseers at sources.redhat.com.
> I expect the pages to be read rarely (one might imagine a marginal
> chance of a slashdot effect tomorrow, but I dunno ...).
I hate to rain on your parade, but I doubt it :-)
Cheers, Ben
next prev parent reply other threads:[~2003-06-11 12:42 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 [this message]
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
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=873cigiyh5.fsf@sashimi.wasabisystems.com \
--to=bje@wasabisystems.com \
--cc=cgen@sources.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).