Message-Id: <5.1.0.14.1.20020915120832.00a083e0@um1b.pce.de>
Date: Sun, 15 Sep 2002 12:19:47 +0200
To: gopher@complete.org
From: Wolfgang Zekoll <wzk@happy-ent.de>
Subject: [gopher] Re: Encouraging MIME types
In-Reply-To: <200209142214.35897.hardburn@runbox.com>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


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

As Cameron mentioned non-gopher+ clients won't be able to detect the MIME type.
But as long as we are talking about MIME for gopher+ we could add a new 
subentry
to the +ADMIN block which tells a gopher+ client the MIME-type:

    +INFO: 0read meF0/readme.txtFgopher.serverF70
    +ADMIN:
     admin: ...
     lastmod: ...
     content-type: text/plain

MIME-types that have no direct gopher type mapping should be announced as
binary type `9' giving gopher0 clients the chance to make an arrangement
based on the extension, gopher+ clients should use the +ADMIN.content-type
mapping.

Regards

Wolfgang Zekoll