Message-ID: <46215FD8.9070206@aaronjangel.us>
Date: Sat, 14 Apr 2007 18:12:24 -0500
From: "Aaron J. Angel" <thatoneguy@aaronjangel.us>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: gopher@complete.org
Subject: [gopher] Re: Mozilla bugs about Gopher, and a dangerous one
References: <701335.48225.qm@web35508.mail.mud.yahoo.com>
In-Reply-To: <701335.48225.qm@web35508.mail.mud.yahoo.com>
Content-type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

JumpJet Mailbox wrote:
> In my surfing I have noticed that not all Gopher Server Administrators
 > are mapping all Item Types in their servers.  Every file extension on
 > their server should be EXPLICITLY mapped to an Item Type.  Below are
 > the standard Item Types understood by most Gopher Clients:
[snip]
> A concientious administrator should also include a listing of what they
 > have mapped on their server.

Not all file systems make consistent (or indeed any) use of extensions. 
  Take, for example, HFS from Mac, UFS or Ext2 from Unix/Linux based 
systems.  Those file systems are completely agnostic to file extensions; 
they don't mean anything to anyone except the operator or user.  The 
same is true with most URLs.  Extensions don't matter.  What gets spit 
out isn't always the same format as the input.  (-:

-- 
Aaron J. Angel.  You know, That One Guy!  <thatoneguy@aaronjangel.us>
Visit me on the web at http://www.aaronjangel.us/.