Received: with LISTAR (v1.0.0; list gopher); Thu, 24 Jan 2002 10:44:42 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from mirth.inuus.com (unknown [209.0.105.71]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id ECF993B81D for ; Thu, 24 Jan 2002 10:44:41 -0500 (EST) Received: (from lindner@localhost) by mirth.inuus.com (8.11.6/8.11.6) id g0OFdlR17506; Thu, 24 Jan 2002 07:39:47 -0800 Date: Thu, 24 Jan 2002 07:39:47 -0800 From: Paul Lindner To: Robert Hahn Cc: Paul Lindner , gopher@complete.org Subject: [gopher] Re: mime types Message-ID: <20020124073947.C13142@inuus.com> Mail-Followup-To: Robert Hahn , gopher@complete.org References: <20020124133041.53764.qmail@ingwaz.pair.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020124133041.53764.qmail@ingwaz.pair.com>; from rhahn@tenletters.com on Thu, Jan 24, 2002 at 01:30:41PM -0000 Content-Transfer-Encoding: 8bit X-archive-position: 394 X-listar-version: Listar v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: lindner@inuus.com Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Listar version 1.0.0 X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher On Thu, Jan 24, 2002 at 01:30:41PM -0000, Robert Hahn wrote: > > > Paul Lindner wrote: > > > > Perhaps when I finish the apache 2.0 gopher server I can see about > > hitching these two together.. > Paul, I don't know if you've done this already, but can you tell us > a bit more about this project? What I'm really curious about is the > thinking behind creating a gopher plugin vs. using a standalone > server. What advantages do you see in such a design? Please correct > my impression: it seems like you're attaching a helium filled balloon > to a rock - not in terms of speed concerns, but in terms of > infrastructure. Well, the apache code base is just much better and faster than the UMN gopherd code. It does pre-forking. It has a nice chain-of-responsibility design pattern for each of the phases. Apache also does a good job of mapping file types, authentication, logging and all that. With Apache 2.0 you can easily plug in to the connection phase. This allows one to parse the incoming gopher request and pass control back to the other phases. > I just had a wacky thought - unrelated to the previous > paragraph. Many of you might have heard that some people have > compiled a web server into the Linux kernel for some impressive > speed gains... I wonder what compiling gopher into the linux kernel > would be like. :) Anyone trying that? Betcha that would make > slashdot... :) A replacement for NFS, perhaps? hmm... -rh That would be TUX.. TUX is great, and it already supports http and ftp, so I guess it wouldn't be a stretch to support gopher.. -- Paul Lindner lindner@inuus.com ||||| | | | | | | | | | mod_perl Developer's Cookbook http://www.modperlcookbook.org Human Rights Declaration http://www.unhchr.ch/udhr/index.htm