Re: [gopher] Selector types summary
On Tue, Mar 08, 2011 at 10:39:05AM +0100, Christoph Lohmann wrote:
> just a summary of the selectors I know:
> Selectors defined in the RFC:
> 0 - textfile
> 1 - menu
> 2 - cso protocol?
> 3 - error
> 4 - Macintosh encoded BINHEX format?
> 5 - PC-DOS binary?
> 6 - uuencoded
> 7 - search
> 8 - telnet
> 9 - binary file
> + - redundant server (mirror)?
> g - GIF file
> I - image file
> T - tn3270 session?
> Selectors seen in the wild:
> h - hypertext link
> i - informational item (text)
> Some questions regarding them:
> What is this CSO protocol? I can't find any specification of it.
> Can someone point me at a still running server?
A phone book directory:
I tried to compile it once, but I was unable to.
> 4, 5, 6 and 9 seem to be redundant for binary files? The only
> difference is, that some old clients may be interested in such
6, strictly speaking, is for files encoded with uuencode which is
itself a text format.
> g and I are redundant for image files?
> How is the + type supposed to work? The balancing server is send-
> ing out a menu with all the redundant servers first and then the
> client decides where to connect?
>From RFC 1436:
The information applies to a duplicated server. The information
contained within is a duplicate of the primary server. The primary
server is defined as the last DirEntity that is has a non-plus
"Type" field. The client should use the transaction as defined by
the primary server Type field.
> 8 and T are redundant for interactive sessions? I would propose
> a selector type for SSH: 's'.
tn3270, evidently, is a different kind of telnet session.
> Christoph Lohmann
Gopher-Project mailing list