Received: with ECARTIS (v1.0.0; list gopher); Tue, 26 Aug 2003 08:23:50 -0500 (CDT) Return-Path: X-Original-To: gopher@complete.org Delivered-To: gopher@complete.org Received: from localhost (localhost [127.0.0.1]) by gesundheit.complete.org (Postfix) with ESMTP id BE96118321BF; Tue, 26 Aug 2003 08:23:47 -0500 (CDT) Received: from gatekeeper.elmer.external.excelhustler.com (gatekeeper.excelhustler.com [68.99.114.105]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "gatekeeper.elmer.external.excelhustler.com", Issuer "excelhustler.com" (not verified)) by gesundheit.complete.org (Postfix) with ESMTP id 07581183219D; Tue, 26 Aug 2003 08:23:35 -0500 (CDT) Received: from chatterbox.elmer.internal.excelhustler.com (unknown [192.168.0.12]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "chatterbox.elmer.internal.excelhustler.com", Issuer "excelhustler.com" (verified OK)) by gatekeeper.elmer.external.excelhustler.com (Postfix) with ESMTP id 49C4EE01A1; Tue, 26 Aug 2003 08:23:33 -0500 (CDT) Received: by chatterbox.elmer.internal.excelhustler.com (Postfix, from userid 102) id 19B095C0CF; Tue, 26 Aug 2003 08:23:33 -0500 (CDT) X-Scanned-By: AMaViS-ng/clamscan at chatterbox.elmer.internal.excelhustler.com Received: from wile.internal.excelhustler.com (wile.internal.excelhustler.com [192.168.1.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by chatterbox.elmer.internal.excelhustler.com (Postfix) with ESMTP id 4CCD85C0C5; Tue, 26 Aug 2003 08:23:32 -0500 (CDT) Received: by wile.internal.excelhustler.com (Postfix, from userid 1000) id E7FEA781C; Tue, 26 Aug 2003 08:23:31 -0500 (CDT) Date: Tue, 26 Aug 2003 08:23:31 -0500 From: John Goerzen To: gopher@complete.org Subject: [gopher] Re: PyGopherd 2.0 released; Gopher and WAP Message-ID: <20030826132331.GA3297@wile.excelhustler.com> References: <20030823201547.GA5036@complete.org> <20030824194612.GC16244@pongonova.net> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030824194612.GC16244@pongonova.net> User-Agent: Mutt/1.4i X-Scanned-By: clamscan at complete.org Content-Transfer-Encoding: 8bit X-archive-position: 800 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 Sun, Aug 24, 2003 at 02:46:12PM -0500, Brian wrote: > On Sat, Aug 23, 2003 at 03:15:47PM -0500, John Goerzen wrote: > > Additionally, there is the debut of a major new feature: the WAP protocol. > > So do you all think this could be the niche that will bring gopher > back to popularity again? I'm not sure, but it sure would be nice. It occured to me after I got a phone that supports WAP -- and I thought it would be really neat to see. It turns out to work very nicely. The fact that Gopher keeps everything simple, and has a well-defined metadata set, means that it turns have a new niche that I don't think anyone saw coming: as a base for other layers on top of it. While we're on the subject, I should describe what I've been experimenting on with PyGopherd lately. I currently have my Gopher site at quux.org, and my Web site at complete.org. The Web site runs under Zope, which I have been attempting to get rid of for ages. Plus, I'd like for more of its content to be available under Gopher, while still having a nice look for Web visitors. (Nicer than PyGopherd currently generates). Putting more of it under Gopher would provide some other benefits, too: such as a nice hierarchical organization for free, plus WAP access for free. So I decided that I would experiment with adding a TAL (aka ZPT or Zope Page Templates) handler to PyGopherd. It turns out that this approach is amazingly powerful. We may just have stumbled on a new web publishing system by accident here :-) I'm going to be spending some time in the next few days experimenting with the system. It took only 67 lines of code in a single file to implement this in PyGopherd and can be completely disabled for those that have no need for it. -- John