Received: with ECARTIS (v1.0.0; list gopher);
 Mon, 16 Sep 2002 21:56:39 -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 DFECA62E66
	for <gopher@complete.org>; Mon, 16 Sep 2002 21:56:37 -0500 (EST)
Received: from [10.9.9.110] (helo=snoopy.runbox.com)
	by tramp.runbox.com with esmtp (Exim 4.05-VA-mm1)
	id 17r8XJ-0006Bc-00
	for gopher@complete.org; Tue, 17 Sep 2002 04:56:25 +0200
Received: from [207.1.1.185] (helo=enterprise)
	(Authenticated Sender=hardburn)
	by snoopy.runbox.com with asmtp (Exim 3.35 #1)
	id 17r8X2-0004MU-00
	for gopher@complete.org; Tue, 17 Sep 2002 04:56:09 +0200
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: Mon, 16 Sep 2002 21:55:54 -0500
X-Mailer: KMail [version 1.4]
References: <200209142214.35897.hardburn@runbox.com>
 <20020916023229.GB25785@complete.org>
In-Reply-To: <20020916023229.GB25785@complete.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200209162155.58117.hardburn@runbox.com>
X-archive-position: 694
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

On Sunday 15 September 2002 21:32, John Goerzen wrote:
> 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.

Oops, you're right.

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

Yes.  I am intentionaly redefining the '0' type to be only text/plain 
documents.

Where was the 'h' type defined?  It wasn't in RFC 1436, and I didn't see it in 
the Gopher+ doc, either.

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

Perhaps.

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

That's the point.  I'd like to progressivly destroy the item type field.  I 
figured that the seperation of GIF files and other image types doesn't make 
sense anymore, so the 'I' attribute would be a good place to start for type 
field deprecation.  The 'g' type is only kept for the benifit of Gopher0 
clients.  For now.

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

It gives a clear indication of what's being actively worked on and what is 
becoming stale.  I basically assume that if a client is not at Gopher+ now 
(or won't be there soon), it's not being activly worked on and should be 
ignored.

- -- 
On two occasions I have been asked [by members of Parliament!], "Pray, Mr. 
Babbage, if you put into the machine wrong figures, will the right answers 
come out?"  I am not able rightly to apprehend the kind of confusion of 
ideas that could provoke such a question.
		--Charles Babbage
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj2Gmb0ACgkQqpueKcacfLTu6gCfT3Wts1ZsNSd5/Ch76/hWYLRQ
X8kAnjRjRtxZPi+z6C7kXdIwwRMMkKKI
=dSJU
-----END PGP SIGNATURE-----