Subject: Re: Suggestion for improving Archives
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Date: Sun, 5 Sep 2004 23:42:29 +1000
Message-ID: <5066E5A966339E42AA04BA10BA706AE56192@rodrick.geeknet.com.au>
Thread-Topic: [pgsql-www] Suggestion for improving Archives
Thread-Index: AcSTS+keph7SSV+RQ4yCVOWBMdoylwAAaeYQ
From: "John Hansen" <john@geeknet.com.au>
To: "Oleg Bartunov" <oleg@sai.msu.su>
Cc: "Greg Sabino Mullane" <greg@turnstep.com>,
	<pgsql-www@postgresql.org>

>=20
> What code ? I've seen that last modified header and now it's gone.
> No stress on the archives, it's pure question of several lines of code
>=20

Yes, which is exactly what we wanted to avoid, more php code.


> it's not a portal page, it's just a message, why should it=20
> changed so often. I think I should teach our crawler to=20
> recognize if changes were cosmetic using fuzzy checksum.
>=20

No, but even something as simple as adding a new mailing list would then
cause you to recrawl the entire site.
I agree that the last-modified header is the best solution. (the value
of it being equal to the message date, that is)


... John