Subject: Re: PostgreSQL web site 
Date: Tue, 29 Aug 2006 05:10:46 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-ID: <C88CF37B2468134A9A28F4B2BFDEBAB901A662@bdc.geeknet.com.au>
In-Reply-To: <15501.1156790439@sss.pgh.pa.us>
Content-class: urn:content-classes:message
Thread-Topic: [pgsql-www] PostgreSQL web site 
Thread-Index: AcbK0YGzLCS+VM2cRPae9NiIi/Q9DwAAuzUQ
From: "John Hansen" <john@geeknet.com.au>
To: "Tom Lane" <tgl@sss.pgh.pa.us>,
	"Magnus Hagander" <mha@sollentuna.net>
Cc: "Joshua D. Drake" <jd@commandprompt.com>,
	"Naz Gassiep" <naz@mira.net>, <pgsql-www@postgresql.org>

Tom Lane Wrote:
>"Magnus Hagander" <mha@sollentuna.net> writes:
>>> Actually that is a very good question... why are we not using=20
>>> mod_deflate?
>
>> Good question. It's definitly worth investigating.
>
> What are we talking about here --- some hack to make users' web =
browsers decompress pages on-the-fly?  How much > does that slow down =
the browsing experience, if you've got an old slow PC?  (I can believe =
that if you've got a > fast PC and a slow internet connection, it could =
make things faster overall ... but the breakeven point is not=20
> obvious.)  What are the odds that people using older browsers will be =
locked out entirely?

Documents are only compressed if the browser requests one, so nobody =
would get locked out.
And for the odd users with a slow PC, they would probably already have =
cofigured their browser so it doesn't request compressed documents.

Kind Regards,

John