Complete.Org: Mailing Lists: Archives: gopher: July 2008:
[gopher] Re: Item Type Suggestions

[gopher] Re: Item Type Suggestions

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Item Type Suggestions
From: Cameron Kaiser <spectre@xxxxxxxxxxxx>
Date: Tue, 22 Jul 2008 05:50:05 -0700 (PDT)
Reply-to: gopher@xxxxxxxxxxxx

> > gopher://
> Does this mean that we have to look up the mime-type for each file? What if
> you don't know it? Also, wouldn't this make it harder to give links to other
> people? I'm not really at peace with these things - mime-types and all that
> just aren't my cup of tea.

It would make them longer, yes. However, the idea here is only to use the
MIME type for ambiguous or unspecified types. A client that is type-aware only
uses the MIME type if it's provided, and falls back on the itemtype otherwise.
A client that doesn't know about MIME types just sees the 9.

This would also need a server that knows the ( ) portion is a directive, not
a portion of the file selector, but that's easy enough of course.

Like I say, the idea here is not to force all URLs to look like this, but to
extend item types without actually adding any, *and* to still work with clients
and existing menus. The idea is purely facultative, not obligatory.

------------------------------------ personal: --
  Cameron Kaiser * Floodgap Systems * * ckaiser@xxxxxxxxxxxx
-- The best things in life are sold out. --------------------------------------

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