Received: with ECARTIS (v1.0.0; list gopher); Thu, 04 Apr 2002 18:39:11 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from tomts6-srv.bellnexxia.net (tomts6.bellnexxia.net [209.226.175.26]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id EC0213B80B for ; Thu, 4 Apr 2002 18:39:10 -0500 (EST) Received: from sympatico.ca ([64.228.207.10]) by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20020404233904.OPKF29105.tomts6-srv.bellnexxia.net@sympatico.ca> for ; Thu, 4 Apr 2002 18:39:04 -0500 Message-ID: <3CACE3A1.464BE377@sympatico.ca> Date: Thu, 04 Apr 2002 18:37:05 -0500 From: Ralph Furmaniak X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: gopher@complete.org Subject: [gopher] Re: Pygopherd nearing gopherd replacement References: <7DFACC96-4822-11D6-857D-0003930BF072@complete.org> Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-archive-position: 556 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: sugaku@sympatico.ca 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 > Pygopherd also does not add > an extra (or "second" if you're using URLs) type character like UMN > gopherd does. Because it figures all this out itself, that is > unnecessary. This does have its uses. For example an executable must be able to return either a plain file or a menu (gophermap format). If you include the character you can also do things such as using type 1 for a file and have it read as a gophermap menu. This character is also used to signify mail spool files. Including the type character can make the code somewhat (albeit not much) simpler and does not cause any problems that I am aware of.