Received: with LISTAR (v1.0.0; list gopher); Thu, 24 Jan 2002 08:30:43 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from ingwaz.pair.com (ingwaz.pair.com [209.68.1.186]) by pi.glockenspiel.complete.org (Postfix) with SMTP id 0DB653B81D for ; Thu, 24 Jan 2002 08:30:43 -0500 (EST) Received: (qmail 53765 invoked by uid 3017); 24 Jan 2002 13:30:41 -0000 Date: 24 Jan 2002 13:30:41 -0000 Message-ID: <20020124133041.53764.qmail@ingwaz.pair.com> To: Paul Lindner , gopher@complete.org From: Robert Hahn Subject: [gopher] Re: mime types X-archive-position: 392 X-listar-version: Listar v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: rhahn@tenletters.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 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. 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