Received: with ECARTIS (v1.0.0; list gopher); Sat, 14 Sep 2002 22:09:38 -0500 (EST) Return-Path: <hardburn@runbox.com> 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 6E49B644D4 for <gopher@complete.org>; Sat, 14 Sep 2002 22:09:36 -0500 (EST) Received: from [10.9.9.9] (helo=fetch.runbox.com) by tramp.runbox.com with esmtp (Exim 4.05-VA-mm1) id 17qPmw-0007sk-00 for gopher@complete.org; Sun, 15 Sep 2002 05:09:34 +0200 Received: from [204.71.148.123] (helo=enterprise) (Authenticated Sender=hardburn) by fetch.runbox.com with asmtp (Exim 3.35 #1) id 17qPmC-0008V6-00 for gopher@complete.org; Sun, 15 Sep 2002 05:08:49 +0200 Content-type: text/plain; charset=us-ascii From: Timm Murray <hardburn@runbox.com> To: gopher@complete.org Subject: [gopher] Encouraging MIME types Date: Sat, 14 Sep 2002 22:14:32 -0500 X-Mailer: KMail [version 1.4] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200209142214.35897.hardburn@runbox.com> X-archive-position: 687 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: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-ID: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

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

Gopher+ makes it possible to use MIME types in a Gopher item. I belive using MIME types in Gopher should be encouraged due to their greater flexibility. A single character item is actually less flexible than the DOS 3 char filename extension.

I'd like to see the following implemented:

1) For backwards compatibility, servers must send the defined type associated with a file if it matches exactly with the type (with the exception layed out in [3]). A file that would have a MIME type of text/text will still have a type of '0', GIF files will still have a type of 'g', etc. Note that files with similar types would *not* use the standard Gopher types. For instance, a text/html document would never be sent as a Gopher type of '0'.

2) A new Gopher type, 'm', is to be implemented which tells a client to check the MIME type in the Gopher+ space.

3) The 'I' type is to be either completely deprecated or used as a synonym for 'm'. GIF files can still use the 'g' type, but any other images should be sent with the 'm' type and their proper MIME type.

4) No new Gopher types are to be defined--MIME types are to be used as a complete replacement. The only possible exception to this is for research purpases, but even then, MIME types are encouraged.

- -- We all know LInux is great . . . it does infinite loops in 5 seconds. --Linus Torvalds -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj2D+xsACgkQqpueKcacfLS10wCgySh6rMnG+hXopJbTt1VBj1/g ikkAn1xy7NzisW0L5sJ3IQiW/eX2nooD =2gBG -----END PGP SIGNATURE-----