<?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);
 Tue, 03 Jan 2006 16:56:56 -0600 (CST)
Received: from relay.peterstar.ru ([217.195.65.5])
	by glockenspiel.complete.org with esmtp
	(Exim 4.50)
	id 1Etv5H-0001FA-4p
	for gopher@complete.org; Tue, 03 Jan 2006 16:56:55 -0600
Received: from home (dialup1-38.Pskov.PeterStar.net [82.140.121.38] (may be
 forged))
	by relay.peterstar.ru (8.13.5/8.11.4) with ESMTP id k03MuZO7043161
	for &lt;gopher@complete.org&gt;; Wed, 4 Jan 2006 01:56:40 +0300 (MSK)
Received: (from rp@localhost)
	by home (8.8.7/8.8.7) id BAA14445
	for gopher@complete.org; Wed, 4 Jan 2006 01:55:35 +0300
Date: Wed, 4 Jan 2006 01:55:34 +0300
From: &quot;R.A.Pavlov&quot; &lt;webmaster@ankylym.ru&gt;
To: gopher@complete.org
Subject: [gopher] Re: PyGopherd and Gopher+
Message-ID: &lt;20060104015534.I421@freeshell.org&gt;
Mail-Followup-To: gopher@complete.org
References: &lt;20051231155642.GA9489@SDF.LONESTAR.ORG&gt;
 &lt;20051231164643.GB28740@katherina.lan.complete.org&gt;
 &lt;20051231173023.GA2684@SDF.LONESTAR.ORG&gt;
 &lt;op.s2pefzakvbderv@wybotnnas01-pool0-a14.wybotn.tds.net&gt;
 &lt;20060101165144.GA2143@SDF.LONESTAR.ORG&gt;
 &lt;op.s2qt03v8vbderv@wybotnnas01-pool0-a61.wybotn.tds.net&gt;
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: &lt;op.s2qt03v8vbderv@wybotnnas01-pool0-a61.wybotn.tds.net&gt;;
 from geph@nerdshack.com on Mon, Jan 02, 2006 at 03:01:41AM -0600
X-SpamTest-Info: Profile: Formal (309/051227)
X-SpamTest-Info: Profile: Detect Hard No RBL (4/030526)
X-SpamTest-Info: Profile: SysLog
X-SpamTest-Info: Profile: Marking Spam - Subject (2/030321)
X-SpamTest-Status: Not detected
X-SpamTest-Version: SMTP-Filter Version 2.1.1 [0150], SpamtestISP/Release
X-Spam-Status: No (score 0.3): AWL=-0.254, WEIRD_PORT=0.507
X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Tue,
 03 Jan 2006 16:56:55 -0600
Content-Transfer-Encoding: 8bit
X-archive-position: 1221
X-ecartis-version: Ecartis v1.0.0
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
X-original-sender: webmaster@ankylym.ru
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>&gt;      A menu would look similar to this,
&gt;
&gt;        &quot;1This points to a gopher
&gt; menu%09/selector%09host%09port%09size%09mimetype&quot;.
&gt;        Where %09 is a hex-encoded tab.
</p>
<p>I would also add encoding for text files and directory listings. Current
servers and clients have so much bugs with Cyrillic and 8-bit chars in
general.
</p>
<p>&gt; 2)  I think new itemtypes should be reserved for file and text uploads.
&gt; The type of upload allowed could be defined in a new tabspace, 0 for
&gt; textfiles, 4 for binhex, 5 for DOS binary, you get the idea.  I&#x27;m
&gt; envisioning things like ftp gateways and bulletin board systems.
</p>
<p>New item types are a compatibility problem, maybe existing types could
be extended instead (e.g. in a way similar to described in my previous
post about GN)?
If it&#x27;s really needed:
In fact gopher bboards and guestbooks are pretty well made with just
sending email and parsing it on server with procmail or other script.
See example of a bboard-like thing
gopher://sdf.lonestar.org/1/users/yargo/glog
I have also set up a gopher guestbook here:
gopher://www.polarhome.com:27070/0/guestbook
</p>
<p>&gt;    These things may already be possible with gopher+, but to loosely quote
&gt; the RFC1436, intelligence should be held by the server, and should not be
&gt; required of the client.  Things like +VIEWS usually require intelligence
&gt; on the part of the USER, who may or may not know whether he wants to
&gt; download a file in plaintext or postscript format.  Essentially, I would
&gt; like to streamline the important features of gopher+ to a single network
&gt; connection and keep the syntax respectful of the original gopher protocol.
&gt;
&gt; --
&gt; Jeff
&gt;
&gt;
</p>
<p>--
Yours, etc.
	Roman A. Pavlov
</p>
<p>gopher://sdf.lonestar.org/1/users/rp
</p>
<p></p>
<p></p>
</card>
</wml>
