Date: Wed, 04 Jan 2006 00:16:53 -0600
From: Jeff <geph@nerdshack.com>
To: gopher@complete.org
Subject: [gopher] Re: PyGopherd and Gopher+
References: <20051231155642.GA9489@SDF.LONESTAR.ORG>
 <20051231164643.GB28740@katherina.lan.complete.org>
 <20051231173023.GA2684@SDF.LONESTAR.ORG>
 <op.s2pefzakvbderv@wybotnnas01-pool0-a14.wybotn.tds.net>
 <20060101165144.GA2143@SDF.LONESTAR.ORG>
 <op.s2qt03v8vbderv@wybotnnas01-pool0-a61.wybotn.tds.net>
 <20060104044609.GB12981@katherina.lan.complete.org>
Content-type: text/plain; charset=iso-8859-15
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-ID: <op.s2ubqfi6vbderv@wybotnnas01-pool0-a222.wybotn.tds.net>
In-Reply-To: <20060104044609.GB12981@katherina.lan.complete.org>
User-Agent: Opera M2/8.51 (Win32, build 7712)
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

On Tue, 03 Jan 2006 22:46:09 -0600, John Goerzen <jgoerzen@complete.org>  
wrote:

>  * It is still a great annoyance to have meta information conveyed
>    by the referring object rather than the object itself.
>
>    I wonder if we may consider extending the protocol so that a
>    request of a certain form would cause a compliant server
>    to send a single line of meta information before sending the
>    document as usual.  This single line of meta information could
>    even be in the form of a regular (gopher++ is it now?) menu line.
>
>    It seems to generally be the case, both in filesystems and in
>    browsers, that meta-information is obtained by the object itself,
>    not the object the refers to it.  IE sometimes looks at the
>    extension of a file to determine what sort of file it is, and this
>    is generally considered a bug.
>
>    By doing this, we could also reform the gopher:// URL schema.
>
> -- John

Gopher 'headers' do seem to be the least obtrusive/best solution.

-- 
Jeff