Received: with ECARTIS (v1.0.0; list gopher); Mon, 02 Jan 2006 03:36:33 -0600 (CST) Received: from relay.peterstar.ru ([217.195.65.5]) by glockenspiel.complete.org with esmtp (Exim 4.50) id 1EtM78-0001bJ-Vm for gopher@complete.org; Mon, 02 Jan 2006 03:36:32 -0600 Received: from home (dialup1-25.Pskov.PeterStar.net [82.140.121.25] (may be forged)) by relay.peterstar.ru (8.13.5/8.11.4) with ESMTP id k029a7gn033359 for ; Mon, 2 Jan 2006 12:36:08 +0300 (MSK) Received: (from rp@localhost) by home (8.8.7/8.8.7) id MAA03554 for gopher@complete.org; Mon, 2 Jan 2006 12:32:26 +0300 Date: Mon, 2 Jan 2006 12:32:24 +0300 From: "R.A.Pavlov" To: gopher@complete.org Subject: [gopher] Re: PyGopherd and Gopher+ Message-ID: <20060102123224.E26748@freeshell.org> Mail-Followup-To: gopher@complete.org References: <200601011724.JAA11584@floodgap.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200601011724.JAA11584@floodgap.com>; from spectre@floodgap.com on Sun, Jan 01, 2006 at 09:24:54AM -0800 X-SpamTest-Info: Profile: Formal (309/051227) X-SpamTest-Info: Profile: Detect Hard No RBL (4/030526) X-SpamTest-Info: Profile: SysLog X-SpamTest-Info: Profile: Marking Spam - Subject (2/030321) X-SpamTest-Status: Not detected X-SpamTest-Version: SMTP-Filter Version 2.1.1 [0150], SpamtestISP/Release X-Spam-Status: No (score 0.0): none X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Mon, 02 Jan 2006 03:36:32 -0600 Content-Transfer-Encoding: 8bit X-archive-position: 1217 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: webmaster@ankylym.ru Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher By the way, I think a nice extension of basic gopher protocol is implemented in GN gopher server - I have just installed it on local machine yesterday, played with it for a while and have been very satisfied - a compact ( about 50Kb binary) and fast server with all the features of UMN gopherd (except gopher+) and a "gophery" way of adding extended features - by adding some extra item types (transparently for the client) - like 7g for embedded grep-like search, 1m for "structured files" presented as directories (as mailbox files), 0h if a HTML version of a file is provided (something like +VIEWS), 7w, 7wc, 7wh etc. for different types of wais searches etc. On Sun, Jan 01, 2006 at 09:24:54AM -0800, Cameron Kaiser wrote: > > 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. ------------------------------------------- > > -- Yours, etc. Roman A. Pavlov gopher://sdf.lonestar.org/1/users/rp