From: Cameron Kaiser <spectre@floodgap.com>
Message-Id: <200601011724.JAA11584@floodgap.com>
Subject: [gopher] Re: PyGopherd and Gopher+
In-Reply-To: <op.s2pefzakvbderv@wybotnnas01-pool0-a14.wybotn.tds.net> from
 Jeff at "Jan 1, 6 08:27:25 am"
To: gopher@complete.org
Date: Sun, 1 Jan 2006 09:24:54 -0800 (PST)
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

>    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: http://www.armory.com/~spectre/ ---
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com
-- Look busy. Jesus is coming soon. -------------------------------------------