Complete.Org: Mailing Lists: Archives: gopher: January 2006:
[gopher] Re: PyGopherd and Gopher+

[gopher] Re: PyGopherd and Gopher+

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: PyGopherd and Gopher+
From: Jeff <geph@xxxxxxxxxxxxx>
Date: Tue, 03 Jan 2006 21:29:37 -0600
Reply-to: gopher@xxxxxxxxxxxx

On Tue, 03 Jan 2006 17:30:41 -0600, Benn Newman  
<newmanbe@xxxxxxxxxxxxxxxx> wrote:

> On Wed, Jan 04, 2006 at 01:55:34AM +0300, R.A.Pavlov wrote:
>> 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.
> See page twelve of RFC 1436, eight-bit encodings are allowed.
>> > 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.
> I think new item types should be used when the existing ones do not  
> provide the required functionilty.
> For example, 9 takes care of everything.
> I would want new item types when you want the behavior of the client to  
> change,
> like a search index (item type 7) to be returned as a plain text file  
> (item type 0).

Would be possible with a new tabspace for mimetypes :)

> I remember seeing that in the source for Squid iirc or something. I guess
> upload would qualify as making the client do something special
> And are file upload really Gopher? :)
>> gopher://
> Your Gopher at is finally working again!


[Prev in Thread] Current Thread [Next in Thread]