From: Cameron Kaiser <spectre@floodgap.com>
Message-Id: <200601040610.WAA12498@floodgap.com>
Subject: [gopher] Re: PyGopherd and Gopher+
In-Reply-To: <op.s2uaq6kavbderv@wybotnnas01-pool0-a222.wybotn.tds.net> from
 Jeff at "Jan 3, 6 11:55:44 pm"
To: gopher@complete.org
Date: Tue, 3 Jan 2006 22:10:06 -0800 (PST)
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

> > > application/x-gopher-* or similar could be reserved through the proper
> > > channels.

> > FWIW, pygopherd internally uses application/gopher-menu and
> > application/gopher+-menu, but it is by no means tied to that.

> A win32 gopher+ client called HGopher also uses those but I didn't see  
> them in any 'official' mimetypes listing.

I think those have been around long enough that they're de-facto ours.
Handling both x-gopher-* and gopher-menu etc. in a client would be trivial
and satisfy both cases.

-- 
--------------------------------- personal: http://www.armory.com/~spectre/ ---
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com
-- Tell the truth, and run. -- Yugoslav proverb -------------------------------