Re: Whack of changes to archives ...
| От | Dave Page |
|---|---|
| Тема | Re: Whack of changes to archives ... |
| Дата | |
| Msg-id | 03AF4E498C591348A42FC93DEA9661B8720544@mail.vale-housing.co.uk обсуждение исходный текст |
| Ответ на | Whack of changes to archives ... ("Marc G. Fournier" <scrappy@postgresql.org>) |
| Ответы |
Re: Whack of changes to archives ...
|
| Список | pgsql-www |
> -----Original Message----- > From: Marc G. Fournier [mailto:scrappy@postgresql.org] > Sent: 20 January 2004 18:17 > To: pgsql-www@postgresql.org > Subject: [pgsql-www] Whack of changes to archives ... > > > Based on comments from Oleg, I did a bunch of cleaning up of > the archives (which is still in the process of being > "re-mhonarced") ... > > First and foremost, a 'Last-Modified' date is now set, based > on the timestamp of the file ... the script that generates > the files is designed so that it doesn't go through and > re-create old messages, so as long as I don't to rebuild the > whole things 'yet again', the time stamps should stay pretty fixed ... > > Second, I added a bunch of code that is aimed at reducing the > amount of information that gets indexed by search engines. > For instance, the banner and search code at the top of > *every* page isn't displayed, nor are the followup/references > stuff at the bottom ... and only the date index is searched, > not the thread ones ... basically, content is presented, not > the miriad of links to that same content ... basically, for > the msg* files, I've strip out *everything* except the > message itself ... Arrggh! You know I'm in the middle of indexing that lot! The banner code etc. can be removed from indexes by wrapping it in <!--noindex--> <!--/noindex--> or similar tags as appropriate to the search engine being used (currently I'm building an ASPSeek index which is proving to work very nicely). Regards Dave.
В списке pgsql-www по дате отправления: