<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
"http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="index" title="Text File" newcontext="true">
<p>
Received: with ECARTIS (v1.0.0; list gopher);
 Sat, 14 Apr 2007 19:31:44 -0500 (CDT)
Received: from web35514.mail.mud.yahoo.com ([66.163.179.138])
	by glockenspiel.complete.org with smtp
	(Exim 4.63)
	id 1Hcsed-0005vA-0c
	for gopher@complete.org; Sat, 14 Apr 2007 19:31:44 -0500
Received: (qmail 66292 invoked by uid 60001); 15 Apr 2007 00:31:36 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=xxLLUfSZzbYM4qAcbpfqb69B5Uw3Bghxut5+G9yUdbkCC3S66e0aQXpF6ikqmmjkE7sDuDQZP4CBd05ZyPAl8dSBq/sEXWMrxkQBUtGk61tf2Tv952oxP9AFMnq/bzTmeV865/l43RxH3Wm0Jl4/UXlPHQwKYvzXAEOAzQ6FScs=;
X-YMail-OSG:
 83gcmLMVM1mAduG23K6E_xsHZ4NeYlILliFQB9dW1BGmJMEsl5.i5_mpINPoDsW88RiN9f2AY5L_0ZjOazB7BRDfHtMTJS_vd0Zg7zUWeDeqF5PJxzC0g4RRpCMdbQ--
Received: from [209.216.94.5] by web35514.mail.mud.yahoo.com via HTTP;
 Sat, 14 Apr 2007 17:31:36 PDT
Date: Sat, 14 Apr 2007 17:31:36 -0700 (PDT)
From: JumpJet Mailbox &lt;jumpjetinfo@yahoo.com&gt;
Subject: [gopher] Re: Mozilla bugs about Gopher, and a dangerous one
To: gopher@complete.org
In-Reply-To: &lt;46215FD8.9070206@aaronjangel.us&gt;
MIME-Version: 1.0
Content-type: text/plain
Content-Transfer-Encoding: 8bit
Message-ID: &lt;286703.63136.qm@web35514.mail.mud.yahoo.com&gt;
X-Spam-Status: No (score 0.9): AWL=0.886, HTML_MESSAGE=0.001
X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Sat,
 14 Apr 2007 19:31:44 -0500
X-archive-position: 1548
X-ecartis-version: Ecartis v1.0.0
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
X-original-sender: jumpjetinfo@yahoo.com
Precedence: bulk
Reply-to: gopher@complete.org
List-help: &lt;mailto:ecartis@complete.org?Subject=help&gt;
List-unsubscribe: &lt;mailto:gopher-request@complete.org?Subject=unsubscribe&gt;
List-software: Ecartis version 1.0.0
List-Id: Gopher &lt;gopher.complete.org&gt;
X-List-ID: Gopher &lt;gopher.complete.org&gt;
List-subscribe: &lt;mailto:gopher-request@complete.org?Subject=subscribe&gt;
List-owner: &lt;mailto:jgoerzen@complete.org&gt;
List-post: &lt;mailto:gopher@complete.org&gt;
List-archive: &lt;http://www.complete.org/mailinglists/archives/&gt;
X-list: gopher
</p>
<p>Windows machines can easily tag Item Type mappings through file &quot;extensions&quot;; and so it is the Windows Server Operators duty to make sure that the appropriate extension is matched to the appropriate file type (i.e., he better not put &quot;.TXT&quot; as the extention of a Binary File).  Other operating systems use other methods to map files to appropriate Item Types.  But whether an OS uses extensions or not, is not the point I&#x27;m trying to make.
What is important is that the Server maps the &quot;Item Type&quot; to APPROPRIATE files SOMEHOW.  HOW the Server or the Server Administrator does it is not the issue.  If, for example, I attempt to download a Binary File, it should not be mapped as a Text File (or my Client will try to open a text reader rather than a download box).
</p>
<p>  The beauty of Gopher, and why it makes surfing easier than with other Protocols, is that a Client can be &quot;dumb&quot;.  A Client doesn&#x27;t have to worry about either &quot;extensions&quot; or &quot;MIME&quot; or anything else; because the Server will (should) take care of dealing with it for the Client.
</p>
<p>  &quot;Aaron J. Angel&quot; &lt;thatoneguy@aaronjangel.us&gt; wrote:
  JumpJet Mailbox wrote:
&gt; In my surfing I have noticed that not all Gopher Server Administrators
&gt; are mapping all Item Types in their servers. Every file extension on
&gt; their server should be EXPLICITLY mapped to an Item Type. Below are
&gt; the standard Item Types understood by most Gopher Clients:
[snip]
&gt; A concientious administrator should also include a listing of what they
&gt; have mapped on their server.
</p>
<p>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&#x27;t mean anything to anyone except the operator or user. The
same is true with most URLs. Extensions don&#x27;t matter. What gets spit
out isn&#x27;t always the same format as the input. (-:
</p>
<p>--
Aaron J. Angel. You know, That One Guy!
Visit me on the web at http://www.aaronjangel.us/.
</p>
<p></p>
<p></p>
<p></p>
<p></p>
<p>---------------------------------
Ahhh...imagining that irresistible &quot;new car&quot; smell?
 Check outnew cars at Yahoo! Autos.
</p>
<p></p>
</card>
</wml>
