Received: with ECARTIS (v1.0.0; list gopher); Thu, 04 Apr 2002 22:47:15 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from pluto2.runbox.com (pluto2.runbox.com [193.71.199.74]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id B6AE43B80B for ; Thu, 4 Apr 2002 22:47:14 -0500 (EST) Received: from mail by pluto2.runbox.com with local (Exim 3.33 #1) id 16tKgy-0001Bx-00 for gopher@complete.org; Fri, 05 Apr 2002 05:47:12 +0200 Content-type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: "Timm Murray" To: gopher@complete.org Subject: [gopher] Re: Pygopherd nearing gopherd replacement Date: Fri, 05 Apr 2002 03:47:12 GMT X-Mailer: RMM Message-Id: X-archive-position: 559 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: hardburn@runbox.com 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 <> > That said, there is no noticeable difference between pygopherd and=20 > gopherd except when rendering very large (hundreds or thousands of=20 > items) UMN-style (dynamically-generated) directories.=20=20 <> Python saves the compiled output of the script after the first run, so new = runs of the=20 script should run at near native speeds anyway.