Complete.Org: Mailing Lists: Archives: gopher: September 2002:
[gopher] Re: Encouraging MIME types
Home

[gopher] Re: Encouraging MIME types

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Encouraging MIME types
From: Timm Murray <hardburn@xxxxxxxxxx>
Date: Mon, 16 Sep 2002 15:14:00 -0500
Reply-to: gopher@xxxxxxxxxxxx

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

On Sunday 15 September 2002 08:31, Thomas Thurman wrote:
> On Sun, 15 Sep 2002, Trevor wrote:
> > Cameron Kaiser wrote:
> > > > 2)  A new Gopher type, 'm', is to be implemented which tells a client
> > > > to check the MIME type in the Gopher+ space.
> > >
> > > This is a nice idea, but what should a non-Gopher+ client do with it?
> >
> > a non-gopher+ client should just ignore it or identify it as an unknown
> > type
>
> Perhaps we could have another type to pass the MIME type into gopher0
> clients: say '^' could mean that the label part of the line contains the
> MIME type of the most recent line of type 'm'.
<snip>

I would assume that any clients that don't support Gopher+ now (or won't do so 
soon) aren't being updated anyway.  So it's rather silly to add anything new 
to the Gopher0 protocol.

- -- 
X windows:  The Cutting Edge of Obsolenscence.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj2GO4sACgkQqpueKcacfLQbfQCgppJWNOvm+So/wLWQzVmhXGCy
clEAmwemI3bklFGzB6KWd0JnVStlA/Bp
=lKin
-----END PGP SIGNATURE-----



[Prev in Thread] Current Thread [Next in Thread]