[gopher] Re: PyGopherd and Gopher+

["R.A.Pavlov" <webmaster@xxxxxxxxxx>]

>      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