Content-type: text/plain; charset=iso-8859-1
From: Timm Murray <hardburn@runbox.com>
To: gopher@complete.org
Subject: [gopher] Re: Encouraging MIME types
Date: Sun, 15 Sep 2002 13:57:37 -0500
References: <200209150516.WAA07128@stockholm.ptloma.edu>
In-Reply-To: <200209150516.WAA07128@stockholm.ptloma.edu>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200209151357.41250.hardburn@runbox.com>
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 15 September 2002 00:16, Cameron Kaiser wrote:
> > 2)  A new Gopher type, 'm', is to be implemented which tells a client to
> > check the MIME type in the Gopher+ space.
>
> This is a nice idea, but what should a non-Gopher+ client do with it?

Non-Gopher+ clients are why currently defined Gopher types should still be 
used (excepting 'I').

- -- 
X windows:  Belongs to the problem set more than the solution set.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj2E2CQACgkQqpueKcacfLTdsQCcDJR7mBqQCxHjgGMLreyqQex0
H28Ani/iBO++xc45TTvmfiUktjnsY+UP
=YR/c
-----END PGP SIGNATURE-----