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 04:50:51 +1000
Message-ID: <5066E5A966339E42AA04BA10BA706AE5618A@rodrick.geeknet.com.au>
Thread-Topic: [pgsql-www] Suggestion for improving Archives
Thread-Index: AcSSp2UXnocM1lcIQdySQlbCOFKSNQAB4+Mg
From: "John Hansen" <john@geeknet.com.au>
To: "Oleg Bartunov" <oleg@sai.msu.su>,
	"Josh Berkus" <josh@agliodbs.com>
Cc: "PostgreSQL WWW Mailing List" <pgsql-www@postgresql.org>

Hi,

>=20
> I could configure search daemon at pgsql.ru to allow search=20
> requests from archives.postgresl.org via perl interface, so=20
> results could be wrapped into any design.
>=20

I currently run search.postgresql.org, and it can be integrated into any
design as well, either using the (ASPseek) method of a html-like
template, or using XSL (the daemon can be configured to output XML).

> >
> > Drop the search interface and replace it with links to pgsql.ru and=20
> > Google Groups.
> >
> > Both of those resources are faster and better search=20
> engines than the Mhonarc
> > search could ever be, and neither eats CPU time on hub.org.   Yes?

However, only one of those resources, pgsql.ru, could be made to make
available new threads on an hourly basis, or maybe even realtime.

Either way, I'm not fuzzed, whichever works the best.

... John