Received: with ECARTIS (v1.0.0; list gopher); Sat, 13 Mar 2004 15:03:36 -0600 (CST) Return-Path: X-Original-To: gopher@complete.org Delivered-To: gopher@complete.org Received: from localhost (localhost [127.0.0.1]) by glockenspiel.complete.org (Postfix) with ESMTP id 3F4CCF9; Sat, 13 Mar 2004 15:03:35 -0600 (CST) Received: from glockenspiel.complete.org ([127.0.0.1]) by localhost (glockenspiel [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id 23691-02; Sat, 13 Mar 2004 15:03:20 -0600 (CST) Received: from erwin.complete.org (unknown [12.149.180.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "erwin.complete.org", Issuer "John Goerzen -- Root CA" (verified OK)) by glockenspiel.complete.org (Postfix) with ESMTP id 9AFEC50; Sat, 13 Mar 2004 15:03:19 -0600 (CST) Received: from katherina.lan.complete.org (katherina.lan.complete.org [10.200.0.4]) by erwin.complete.org (Postfix) with ESMTP id AE7611612; Sat, 13 Mar 2004 15:03:11 -0600 (CST) Received: by katherina.lan.complete.org (Postfix, from userid 1000) id 8EE0A1B001; Sat, 13 Mar 2004 15:03:11 -0600 (CST) Date: Sat, 13 Mar 2004 15:03:11 -0600 From: John Goerzen To: gopher@complete.org Subject: [gopher] Re: Gopherd or pygopherd? Message-ID: <20040313210311.GA10755@complete.org> References: Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1+cvs20040105i X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at complete.org Content-Transfer-Encoding: 8bit X-archive-position: 886 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, Mar 13, 2004 at 03:42:27PM +0100, Alessandro Selli wrote: > I'm just now getting interested in Gopher and I'm currently running > a gopherd 3.0.3 server. Since it's running on a slow machine (Sparc5-85), > would you recommend a C-compiled binary server like gopherd or do you think I > will not notice a big difference in system load/ memory consumption running > an interpreted server like pygopherd? The server is not serving a community > and the Sparc5 is quite beefed up with ram (232MB). Are there other > differences between those two that I should be aware of to choose the correct > server for my site? Gopherd is no longer maintained. Security holes were being found in it on a regular basis, and nobody really had the inclination to give it a thorough security audit given the fact that more advanced Gopher servers existed. Therefore, I would strongly urge you *NOT* to deploy UMN Gopherd. PyGopherd is, to a great extent, completely compatible with UMN Gopherd, and in many cases, is a drop-in replacement for it. Being written in Python, it is immune to a whole class of security bugs that plague not just Gopherd but other C-based servers as well. You should have no problems at all running Pygopherd on that machine. For a project such as a Gopher server, Python will not cause any noticable performance changes. You may be interested that some quite high-capacity servers, such as the Zope web application server, are written in Python and do not suffer performance problems. There are several Gopher servers out there. As the author of PyGopherd, I may be biased here, but I'd say that PyGopherd is the most featureful at present, due to its support for most features of both the UMN and Bucktooth servers. However, if you want something that is quick to set up and maintain, without a lot of bells and whistles, you may want to check into one of the alternatives (or at least disable a bunch of PyGopherd modules). PyGopherd also supports Gopher+, HTTP, and WAP as optional features, and if enabled, will serve your gopher content using those protocols as well -- all over a single port (70 by default). -- John