Received: with ECARTIS (v1.0.0; list gopher); Thu, 04 Apr 2002 19:50:55 -0500 (EST) Return-Path: <jgoerzen@complete.org> Delivered-To: gopher@complete.org Received: from christoph.complete.org (pcp947166pcs.cstltn01.in.comcast.net [68.58.145.248]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id F298B3B80B for <gopher@complete.org>; Thu, 4 Apr 2002 19:50:44 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by christoph.complete.org (Postfix) with ESMTP id 8649D5A313 for <gopher@complete.org>; Thu, 4 Apr 2002 19:50:45 -0500 (EST) Date: Thu, 4 Apr 2002 19:50:45 -0500 Subject: [gopher] Re: Pygopherd in background Content-type: text/plain; charset=US-ASCII Mime-Version: 1.0 (Apple Message framework v481) From: John Goerzen <jgoerzen@complete.org> To: gopher@complete.org Content-Transfer-Encoding: 8bit In-Reply-To: <4196825B-4829-11D6-B899-0030654C9DF2@mac.com> Message-Id: <298043CE-482F-11D6-857D-0003930BF072@complete.org> X-Mailer: Apple Mail (2.481) X-archive-position: 558 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: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-ID: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

On Thursday, April 4, 2002, at 07:08 PM, Clint Paden wrote:

> pygopherd is working great for me so far, I enjoy the improvements. > However, I do not know all that much about Python. What I would like to

Take a look at www.python.org.

> know is is there any way to run pygopherd in the background or as a > daemon of some sort? If so how? If not, can it in the future? Also, what

That capability is not natively present in pygopherd at this time, but it will be. In the meantime, you can just run:

./pygopherd &

The & will put it in the background.

> was the rationale for writing it in python as opposed to C or something > more commonplace (relatively)? Thanks!

Several things. For one, Python provided a lot of useful libraries and utilites. It comes with a nice library for figuring out MIME types, for instance. Python also is not vulnerable to buffer overflow attacks, one of the most common security problems in C code. Python also has a very nice OO system, meaning that a modular architecture is quite easily possible. Several pygopherd classes inherit from each other, and the HandlerMultiplexer and ProtocolMultiplexer classes have a lot of power, not all of which is being used yet. I'm planning to implement virtual folders, which will essentially nest a HandlerMultiplexer with its own root and/or config inside an existing system. Will be great for mirrors with their own .Links files referring to / on the system or for ones where you'd rather just turn off standard MIME type checking and make everything a text file even if it ends in .gif...

-- John