Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: A counter productive conversation about search.
Date: Tue, 29 Aug 2006 15:54:10 +0100
Message-ID: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E40154C8BE@ratbert.vale-housing.co.uk>
In-Reply-To: <44F44EF5.3090102@commandprompt.com>
Thread-Topic: [pgsql-www] A counter productive conversation about search.
thread-index: AcbLd1PrpLK/YOqIQdarsvqxvVDnYgAAlwXA
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: "PostgreSQL WWW" <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Joshua D. Drake [mailto:jd@commandprompt.com]=20
> Sent: 29 August 2006 15:28
> To: Dave Page
> Cc: PostgreSQL WWW
> Subject: Re: [pgsql-www] A counter productive conversation=20
> about search.
>=20
>=20
> >> So is anyone up for helping develop a page grabber?
> >=20
> > We have one - it builds the static version of the main site=20
> by spidering
> > it hourly.
>=20
> Should we look at that then?

Is that the "Royal" we? I'm currently in 'no more project atm' mode, but
as far as I'm concerned you're welcome to work on it yourself on the
understanding that whatever you come up with will only be accepted to
replace the current solution if the community (-www) agrees that it is
a) better from a user perspective, b) more maintainable and c) matches
the main site look'n'feel.

FWIW, one of the problems with building a true online index of the
archives is that we don't know what URL a message might have until it
has been indexed by the archives site. Currently that is then indexed by
ASPSeek sometime later. It might be worth considering rewriting both the
archives and the search to make it all truly realtime. That shouldn't be
terribly difficult apart from generating thread indexes/forward/back
links, and dealing with the historic URL problem. A SMOP you might
say...

:-p

Regards, Dave.