Date: Wed, 4 Jan 2006 01:55:34 +0300
From: "R.A.Pavlov" <webmaster@ankylym.ru>
To: gopher@complete.org
Subject: [gopher] Re: PyGopherd and Gopher+
Message-ID: <20060104015534.I421@freeshell.org>
Mail-Followup-To: gopher@complete.org
References: <20051231155642.GA9489@SDF.LONESTAR.ORG>
 <20051231164643.GB28740@katherina.lan.complete.org>
 <20051231173023.GA2684@SDF.LONESTAR.ORG>
 <op.s2pefzakvbderv@wybotnnas01-pool0-a14.wybotn.tds.net>
 <20060101165144.GA2143@SDF.LONESTAR.ORG>
 <op.s2qt03v8vbderv@wybotnnas01-pool0-a61.wybotn.tds.net>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <op.s2qt03v8vbderv@wybotnnas01-pool0-a61.wybotn.tds.net>;
 from geph@nerdshack.com on Mon, Jan 02, 2006 at 03:01:41AM -0600
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

>      A menu would look similar to this,
> 
>        "1This points to a gopher  
> menu%09/selector%09host%09port%09size%09mimetype".
>        Where %09 is a hex-encoded tab.

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.
 
> 2)  I think new itemtypes should be reserved for file and text uploads.   
> The type of upload allowed could be defined in a new tabspace, 0 for  
> textfiles, 4 for binhex, 5 for DOS binary, you get the idea.  I'm  
> envisioning things like ftp gateways and bulletin board systems.

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'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
 
>    These things may already be possible with gopher+, but to loosely quote  
> the RFC1436, intelligence should be held by the server, and should not be  
> required of the client.  Things like +VIEWS usually require intelligence  
> on the part of the USER, who may or may not know whether he wants to  
> download a file in plaintext or postscript format.  Essentially, I would  
> like to streamline the important features of gopher+ to a single network  
> connection and keep the syntax respectful of the original gopher protocol.
> 
> -- 
> Jeff
> 
> 

-- 
Yours, etc.
	Roman A. Pavlov

gopher://sdf.lonestar.org/1/users/rp