Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: PostgreSQL web site 
Date: Mon, 28 Aug 2006 21:12:30 +0200
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCEA0FB7E@algol.sollentuna.se>
In-Reply-To: <15501.1156790439@sss.pgh.pa.us>
Thread-Topic: [pgsql-www] PostgreSQL web site 
Thread-Index: AcbK0XuR5OG3gdg9QkO1bfoNWDnU0gABEC8Q
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Joshua D. Drake" <jd@commandprompt.com>,
	"Naz Gassiep" <naz@mira.net>, <pgsql-www@postgresql.org>

> >> Actually that is a very good question... why are we not using=20
> >> mod_deflate?
>=20
> > Good question. It's definitly worth investigating.
>=20
> What are we talking about here --- some hack to make users'=20
> web browsers decompress pages on-the-fly?=20
Yes.

> How much does that=20
> slow down the browsing experience, if you've got an old slow=20
> PC?  (I can believe that if you've got a fast PC and a slow=20
> internet connection, it could make things faster overall ...=20
> but the breakeven point is not obvious.)=20

In most cases it's faster or unnoticably slower. At the speed your
machine would have to be to notice the problem, I don't think you can
load a modern-enough browser to actually look at the site.

> What are the odds=20
> that people using older browsers will be locked out entirely?

They should be zero, if you use mod_deflate.
The browser sends an Accept-encoding: deflate (or similar, I'm not 100%
on the name of the header, and too lazy to look it up). If this is not
present in the request, an uncompressed version of the page is sent back
to the browser.

//Magnus