Received: with ECARTIS (v1.0.0; list gopher); Sat, 31 Dec 2005 12:41:02 -0600 (CST) Received: from mo-69-69-114-6.sta.sprint-hsd.net ([69.69.114.6] helo=erwin.lan.complete.org) by glockenspiel.complete.org with esmtps (with TLS-1.0:RSA_AES_256_CBC_SHA:32) (TLS peer CN erwin.complete.org, certificate verified) (Exim 4.50) id 1Eslf2-0000Kt-P6; Sat, 31 Dec 2005 12:41:01 -0600 Received: from katherina.lan.complete.org ([10.200.0.4]) by erwin.lan.complete.org with esmtps (with TLS-1.0:RSA_AES_256_CBC_SHA:32) (No TLS peer certificate) (Exim 4.50) id 1Eslev-0005Vg-BP; Sat, 31 Dec 2005 12:40:53 -0600 Received: from jgoerzen by katherina.lan.complete.org with local (Exim 4.60) (envelope-from ) id 1Eslev-0005c2-1x; Sat, 31 Dec 2005 12:40:53 -0600 Date: Sat, 31 Dec 2005 12:40:52 -0600 From: John Goerzen To: gopher@complete.org Subject: [gopher] Re: PyGopherd and Gopher+ Message-ID: <20051231184052.GA21531@katherina.lan.complete.org> References: <20051231155642.GA9489@SDF.LONESTAR.ORG> <20051231164643.GB28740@katherina.lan.complete.org> <20051231173023.GA2684@SDF.LONESTAR.ORG> MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051231173023.GA2684@SDF.LONESTAR.ORG> User-Agent: Mutt/1.5.11 X-Spam-Status: No (score 0.1): AWL=0.008, FORGED_RCVD_HELO=0.05 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Sat, 31 Dec 2005 12:41:01 -0600 Content-Transfer-Encoding: 8bit X-archive-position: 1209 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org 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 On Sat, Dec 31, 2005 at 11:30:23AM -0600, Benn Newman wrote: > > In general, let me say that after implementing at least part of > > Gopher+ in PyGopherd, I've come to the conclusion that it isn't very > > "Gophery". It's rather complex in some cases and there are a lot of > > special cases. > Bah! UMN said it was Gophery, so there. :-) > > That said, you can probably specify a custom +VIEWS block using the > > PyGopherd general method for specifying custom Gopher+ blocks, but I > > have never tested that. > That would work if you didn't feel like changing the files size everytime > you edited it. True. I guess I'm just lazy. Feel free to send patches ;-) > > You could create a .admin file in the directory, I think. (Again, > > untested, but that should do the trick.) > You can, but that replaces the other information, like the last > modified date. Hmm. Point. Patches will again be accepted ;-) Sorry to say that, but I'm really to the point where PyGopherd does more than I need it to, and don't have a lot of time to add features that I don't need right now, > > It does the correct thing according to gopherd(8). As far as I can > > tell, nobody actually follows what the Gopher+ chapter says on that, > I do. :) > > Johm: I don't know how we call you our leader! *sobs* ;) Probably because you put the word "terrible" before "leader". Not that it isn't true ;-) > (By the way, quux.org's DN seems to be broken.) Its DN? I know that term from LDAP, but I seem to be missing something...