public inbox for [email protected]  
help / color / mirror / Atom feed
From: Dave Page <[email protected]>
To: Marc G. Fournier <[email protected]>
To: Oleg Bartunov <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Postgresql.org search engine.
Date: Mon, 2 Feb 2004 13:39:36 -0000
Message-ID: <[email protected]> (raw)

 

> -----Original Message-----
> From: Marc G. Fournier [mailto:[email protected]] 
> Sent: 01 February 2004 22:12
> To: Oleg Bartunov
> Cc: Marc G. Fournier; Josh Berkus; Dave Page; [email protected]
> Subject: Re: [pgsql-www] Postgresql.org search engine.
> 
> And let me know if the headers look right to you ... I took 
> out the Cache-control stuff ...
> 
> Let me know if there is anything else you'd like to see in there ...

It looks even more complex to me now - there are what, 6 include files?

How about something more simple:

========================================================================
======
<?
  $last_modified = "Fri,  9 Jan 2004 19:00:28 +0000 (GMT)";
  $subject = " Re: IMPORTANT: A temporary list for Strategic Marketing";
  require("$DOCUMENT_ROOT/includes/header.php");
?>

<pre>Joshua D. Drake wrote:
&gt;
&gt; &gt;There shouldn't be any tangents or general discussion on
-advocacy
&gt; &gt;either -- that's what -general is for.  A one-time incident
should not
&gt; &gt;lead to such drastic measures.  If the marketing plan is no
longer
&gt; &gt;discussed on -advocacy, what is?
&gt; &gt;
&gt; &gt;
&gt; I disagree whole heartedly. If you look at general, it is basically
&gt; PostgreSQL-Support.

<!--noindex-->
<HR>
<UL>
<li>Prev by Date:
<strong><a href="msg00116.php">Re: IMPORTANT: A temporary list for
Strategic Marketing</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00118.php">Re: IMPORTANT: A temporary list for
Strategic Marketing</a></strong>
</li>

<li>Previous by thread:
<strong><a href="msg00126.php">Re: IMPORTANT: A temporary list for
Strategic</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00125.php">Re: IMPORTANT: A temporary list for
Strategic</a></strong>
</li>

  <LI>Index(es):
      <UL>
        <LI><A HREF="mail2.php#00117"><STRONG>Main</STRONG></A></LI>
        <LI><A HREF="thrd2.php#00117"><STRONG>Thread</STRONG></A></LI>
      </UL>
  </LI>
</UL>
<!--/noindex-->

<?
  require("$DOCUMENT_ROOT/includes/footer.php");
?>
========================================================================
======

Header.php then may look something like:

========================================================================
======
<?
  if(isset($last_modified)) {
    header("Last-Modified: $last_modified");
  } else {
    header("Last-Modified: " .date("r", filemtime($SCRIPT_FILENAME)));
  }

  // Other stuff here
?>

<HTML>
<HEADER>
  <TITLE><? php echo $subject ?></TITLE>
  <META NAME="robots" CONTENT="nofollow, index, archive">
</HEADER>

<BODY>

<!--noindex-->
  <!-- HTML code for search form etc. -->
<!--/noindex-->
========================================================================
======


And footer.php (minus and footers we might add).

========================================================================
======
</BODY>
</HTML>
========================================================================
======

In addition, there is an awful lot of HTML comments that mhonarc has
added:

<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->

As examples. These seem somewhat extranous and could be removed for ease
of reading and disk space/bandwidth usage reduction.

Oh, and on the current version the noindex tags seem to be in the wrong
places. On the index/thread pages for example, they should enclose all
the hyperlinks. The noindex tags do not stop links being followed, just
the text within them from being included in the index.

Regards, Dave.



view thread (18+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Postgresql.org search engine.
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox