<?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 LISTAR (v1.0.0; list gopher);
 Mon, 11 Feb 2002 16:54:41 -0500 (EST)
Return-Path: &lt;x@mothra.dyndns.org&gt;
Delivered-To: gopher@complete.org
Received: from mothra.dyndns.org (pool-141-152-12-174.rich.east.verizon.net
 [141.152.12.174])
	by pi.glockenspiel.complete.org (Postfix) with ESMTP id EEF143B83E
	for &lt;gopher@complete.org&gt;; Mon, 11 Feb 2002 16:54:40 -0500 (EST)
Received: from x by mothra.dyndns.org with local (Exim 3.34 #1 (Debian))
	id 16aOMu-0007Xk-00
	for &lt;gopher@complete.org&gt;; Mon, 11 Feb 2002 16:52:12 -0500
Date: Mon, 11 Feb 2002 16:52:12 -0500
From: David Allen &lt;mda@idatar.com&gt;
To: gopher@complete.org
Subject: [gopher] Re: Gopher wishlist
Message-ID: &lt;20020211165212.A28993@mothra.dyndns.org&gt;
References: &lt;3C682904.BF4BE07D@sympatico.ca&gt;
 &lt;20020211161035.A28611@mothra.dyndns.org&gt; &lt;3C6838E2.C2902027@sympatico.ca&gt;
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: &lt;3C6838E2.C2902027@sympatico.ca&gt;;
 from sugaku@sympatico.ca on Mon, Feb 11, 2002 at 04:34:26PM -0500
Content-Transfer-Encoding: 8bit
X-archive-position: 428
X-listar-version: Listar v1.0.0
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
X-original-sender: mda@idatar.com
Precedence: bulk
Reply-to: gopher@complete.org
List-help: &lt;mailto:listar@complete.org?Subject=help&gt;
List-unsubscribe: &lt;mailto:gopher-request@complete.org?Subject=unsubscribe&gt;
List-software: Listar version 1.0.0
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></p>
<p>On Mon, Feb 11, 2002 at 04:34:26PM -0500, Ralph Furmaniak wrote:
&gt;
&gt; I do not quite agree about backwards compatability.  Gopher+ was
&gt; designed to be
&gt; backwards compatible, but if you look you&#x27;ll see that the client request
&gt; specifically signals whether it be gopher0 or gopher+, and the
&gt; server sends back
&gt; different data depending.  umn gopher client (AFAIK) always sends a
&gt; &#x27;$&#x27; request
&gt; to the server, and the umn server then sends back something that
&gt; would cause a gopher0 client to choke and die.
</p>
<p>Unfortunately, one of the things that isn&#x27;t specified by the Gopher+
spec as far as I know is whether or not clients should communicate
with gopher+ if they&#x27;re capable of it.
</p>
<p>For example, I wrote a client that always sends gopher0 requests, and
only sends gopher+ requests when it can tell from how the server
responds that the server supports gopher+.  In other words, I&#x27;m trying
to be &quot;polite&quot; by not spewing gopher+ unless I have evidence the other
end supports it.  One thing I would like to see in any future gopher
spec is a solid statement that if you speak protocol X, you should
always speak it, or sometimes speak it depending on what the server
says.  Just nail it down.
</p>
<p>As for backwards compatibility, I guess some would say that gopher is
small now relative to other things, and that if we&#x27;re going to make
changes they should be now.  Others think that making changes and
breaking backwards compatibility threatens to alienate the few people
who do still use gopher.  I tend to be in the latter camp, but I&#x27;m not
immune to good arguments, I guess I just haven&#x27;t seen a feature yet that
was sufficiently needed and sufficiently difficult to implement
without breaking backwards compatibility.
</p>
<p>&gt;
&gt; What could be put into the header/metadata?  I don&#x27;t know.  I&#x27;m sure
&gt; many people
&gt; would be against implementing cookies &lt;g&gt;.  There could be a title included
&gt; (might be some benefits, might not.  depends on the client), and maybe a
&gt; content-type.  I guess there isn&#x27;t much use; gopher already has sufficient
&gt; capabilities.
</p>
<p>Content-type might be nice.  Although I like the translators in UMN
gopherd, it still kinda bugs me when I request, say, FOOBAR.txt.gz
from some server, where it&#x27;s 2142 bytes, and I end up getting text,
(not gzipped text) back, and 44014 bytes.  :)
</p>
<p>--
David Allen
http://opop.nols.com/
----------------------------------------
&quot;If you go on with this nuclear arms race, all you are going to do is
make the rubble bounce&quot;
- Winston Churchill
</p>
</card>
</wml>
