Re: Postgresql.org search engine. - Mailing list pgsql-www

From Dave Page
Subject Re: Postgresql.org search engine.
Date
Msg-id 03AF4E498C591348A42FC93DEA9661B87206B9@mail.vale-housing.co.uk
Whole thread Raw
In response to Postgresql.org search engine.  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgsql-www

> -----Original Message-----
> From: Marc G. Fournier [mailto:scrappy@postgresql.org]
> Sent: 31 January 2004 06:15
> To: Josh Berkus
> Cc: Oleg Bartunov; Dave Page; pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] Postgresql.org search engine.
>
>
>
> I'm kinda curious here ... exactly what problem are we trying
> to solve here?
>

My thoughts as well as we are starting to see suggestions for solving
non-existant problems :-)

1) We need each message file minimised - e.g. some php variables
defined, a php include for the header, the message and thread links and
a php include for the footer.

2) The php header file should use the variables defined in the messages
to generate the <TITLE></TITLE> tag and last modified dates, as well as
any other useful meta data.

3) The php header and footer files should include
<!--noindex--><!--/noindex--> tags to allow aspseek to cache the entire
page but only index the relevant content (see anywhere on the main
portal site to see how this is done - specifically, menus are not
indexed though they are still followed).

4) (Optionally, I don't think it's necessary - certainly not for
ASPSeek) The php header/footer may only display if certain user agent
strings are not detected.

Regards, Dave.

pgsql-www by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: Postgresql.org search engine.
Next
From: www@www.postgresql.com (World Wide Web Owner)
Date:
Subject: New Event