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: Cameron Kaiser <spectre@xxxxxxxxxxxx>
Date: Sun, 1 Jan 2006 09:24:54 -0800 (PST)
Reply-to: gopher@xxxxxxxxxxxx

>    I think gopher+ stinks anyway.  Instead of opening a new connection to  
> fetch the new (mostly undefined) attributes it would have been easier to  
> keep reserving extra tabspaces in the menus for simple things like  
> mimetype and filesize.  My reason for not adding gopher+ to GopherJ is  
> that it doesn't compliment the original protocol.  And as Mr. Goerzen  
> said, it's not very gophery.

I agree. I would have much preferred simply extending the tabspaces. Even
ASK-type blocks could be emulated in some fashion with this.

--------------------------------- personal: ---
  Cameron Kaiser * Floodgap Systems * * ckaiser@xxxxxxxxxxxx
-- Look busy. Jesus is coming soon. -------------------------------------------

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