<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
"http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="index" title="Text File" newcontext="true">
<p>
Received: with ECARTIS (v1.0.0; list gopher);
 Mon, 16 Sep 2002 15:08:47 -0500 (EST)
Return-Path: &lt;hardburn@runbox.com&gt;
Delivered-To: gopher@complete.org
Received: from aibo.runbox.com (aibo.runbox.com [193.71.199.94])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(Client did not present a certificate)
	by gesundheit.complete.org (Postfix) with ESMTP id E98CD64460
	for &lt;gopher@complete.org&gt;; Mon, 16 Sep 2002 15:08:46 -0500 (EST)
Received: from [10.9.9.9] (helo=fetch.runbox.com)
	by tramp.runbox.com with esmtp (Exim 4.05-VA-mm1)
	id 17r2Am-0007x1-00
	for gopher@complete.org; Mon, 16 Sep 2002 22:08:44 +0200
Received: from [208.166.200.157] (helo=enterprise)
	(Authenticated Sender=hardburn)
	by fetch.runbox.com with asmtp (Exim 3.35 #1)
	id 17r2AE-0002Ts-00
	for gopher@complete.org; Mon, 16 Sep 2002 22:08:10 +0200
Content-type: text/plain; charset=iso-8859-1
From: Timm Murray &lt;hardburn@runbox.com&gt;
To: gopher@complete.org
Subject: [gopher] Re: Encouraging MIME types
Date: Mon, 16 Sep 2002 15:14:00 -0500
X-Mailer: KMail [version 1.4]
References:
 &lt;Pine.LNX.4.21.0209151425340.17699-100000@pinkstuff.publication.org.uk&gt;
In-Reply-To:
 &lt;Pine.LNX.4.21.0209151425340.17699-100000@pinkstuff.publication.org.uk&gt;
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: &lt;200209161514.04390.hardburn@runbox.com&gt;
X-archive-position: 693
X-ecartis-version: Ecartis v1.0.0
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
X-original-sender: hardburn@runbox.com
Precedence: bulk
Reply-to: gopher@complete.org
List-help: &lt;mailto:ecartis@complete.org?Subject=help&gt;
List-unsubscribe: &lt;mailto:gopher-request@complete.org?Subject=unsubscribe&gt;
List-software: Ecartis version 1.0.0
List-ID: Gopher &lt;gopher.complete.org&gt;
X-List-ID: Gopher &lt;gopher.complete.org&gt;
List-subscribe: &lt;mailto:gopher-request@complete.org?Subject=subscribe&gt;
List-owner: &lt;mailto:jgoerzen@complete.org&gt;
List-post: &lt;mailto:gopher@complete.org&gt;
List-archive: &lt;http://www.complete.org/mailinglists/archives/&gt;
X-list: gopher
</p>
<p></p>
<p>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
</p>
<p>On Sunday 15 September 2002 08:31, Thomas Thurman wrote:
&gt; On Sun, 15 Sep 2002, Trevor wrote:
&gt; &gt; Cameron Kaiser wrote:
&gt; &gt; &gt; &gt; 2)  A new Gopher type, &#x27;m&#x27;, is to be implemented which tells a client
&gt; &gt; &gt; &gt; to check the MIME type in the Gopher+ space.
&gt; &gt; &gt;
&gt; &gt; &gt; This is a nice idea, but what should a non-Gopher+ client do with it?
&gt; &gt;
&gt; &gt; a non-gopher+ client should just ignore it or identify it as an unknown
&gt; &gt; type
&gt;
&gt; Perhaps we could have another type to pass the MIME type into gopher0
&gt; clients: say &#x27;^&#x27; could mean that the label part of the line contains the
&gt; MIME type of the most recent line of type &#x27;m&#x27;.
&lt;snip&gt;
</p>
<p>I would assume that any clients that don&#x27;t support Gopher+ now (or won&#x27;t do so
soon) aren&#x27;t being updated anyway.  So it&#x27;s rather silly to add anything new
to the Gopher0 protocol.
</p>
<p>- --
X windows:  The Cutting Edge of Obsolenscence.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
</p>
<p>iEYEARECAAYFAj2GO4sACgkQqpueKcacfLQbfQCgppJWNOvm+So/wLWQzVmhXGCy
clEAmwemI3bklFGzB6KWd0JnVStlA/Bp
=lKin
-----END PGP SIGNATURE-----
</p>
<p></p>
</card>
</wml>
