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: Benn Newman <newmanbe@xxxxxxxxxxxxxxxx>
Date: Wed, 4 Jan 2006 07:42:34 -0600
Reply-to: gopher@xxxxxxxxxxxx

On Tue, Jan 03, 2006 at 10:39:04PM -0600, John Goerzen wrote:
> On Mon, Jan 02, 2006 at 09:01:18AM -0600, Benn Newman wrote:
> > The nice thing abous Gopher+ blocks is that they can hold arbitrary
> > information. Do we want to limit ourselves like this?
> That is also a curse, because how do we display arbitrary information?
> (Especially in something that was to be a network-wide filesystem)
If I rememer the Gopher+ spec correctly, it says that the information
should be stadardised. Since it is a plain text file, you can also
display it as that, though I do see your point.
Benn Newman | newmanbe@xxxxxxxxxxxxxxxx | gopher://
Wisconsin Association of Gopher Operators
Learn about the Gopher Project:
-- Attached file included as plaintext by Ecartis --

Version: GnuPG v1.4.1 (NetBSD)


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