Received: with ECARTIS (v1.0.0; list gopher); Sun, 15 Sep 2002 21:32:53 -0500 (EST) Return-Path: <jgoerzen@complete.org> Delivered-To: gopher@complete.org Received: from christoph.complete.org (0-1pool248-3.nas17.topeka2.ks.us.da.qwest.net [65.144.248.3]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "christoph.complete.org", Issuer "John Goerzen -- Root CA" (verified OK)) by gesundheit.complete.org (Postfix) with ESMTP id 750A26446C; Sun, 15 Sep 2002 21:32:51 -0500 (EST) Received: by christoph.complete.org (Postfix, from userid 1000) id 83BA92B77F; Sun, 15 Sep 2002 21:32:29 -0500 (EST) Date: Sun, 15 Sep 2002 21:32:29 -0500 From: John Goerzen <jgoerzen@complete.org> To: gopher@complete.org Subject: [gopher] Re: Encouraging MIME types Message-ID: <20020916023229.GB25785@complete.org> References: <200209142214.35897.hardburn@runbox.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209142214.35897.hardburn@runbox.com> User-Agent: Mutt/1.4i Content-Transfer-Encoding: 8bit X-archive-position: 692 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org 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

On Sat, Sep 14, 2002 at 10:14:32PM -0500, Timm Murray wrote:

> text/text will still have a type of '0', GIF files will still have a type

I assume you mean text/plain.

> 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'.

text/html is type 'h' anyway. However, type 0 is defined to include more than you are defining it to mean.

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

A Gopher+-aware client should already be doing this; there is no need to explicitly tell it to.

> 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.

This breaks backwards compatibility, I suspect.

> 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.

I can agree with that :-)

However, overall, I don't really see any benefit to the 'm' type or the change in meanings for '0' and 'I'. Gopher+ clients should already be using the Gopher+ attributes (in fact, since views permit one menu entry to actually have multiple MIME types, they *must*). Gopher0 clients are still left with the single-character types, which I agree are a nasty thing. I don't see what purpose breaking some of the gopher0 clients will serve, I guess.

-- John