Received: with ECARTIS (v1.0.0; list gopher); Wed, 02 May 2007 10:32:55 -0500 (CDT) Received: from 85-10-193-136.clients.your-server.de ([85.10.193.136]) by glockenspiel.complete.org with esmtp (Exim 4.63) id 1HjGp3-0006r4-BU for gopher@complete.org; Wed, 02 May 2007 10:32:55 -0500 Received: from localhost (port-ip-213-211-226-171.reverse.mdcc-fun.de [213.211.226.171]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by 85-10-193-136.clients.your-server.de (Postfix) with ESMTP id 1DCC738049B24 for ; Wed, 2 May 2007 17:32:16 +0200 (CEST) Date: Wed, 2 May 2007 17:32:49 +0200 From: Christoph Lohmann <20h@r-36.net> To: gopher@complete.org Subject: [gopher] Re: Gopherfs and stuff Message-ID: <20070502173249.37620096@localhost> In-Reply-To: <200705021240.l42Ce4S2016798@floodgap.com> References: <20070502075856.6252b9cf@localhost> <200705021240.l42Ce4S2016798@floodgap.com> X-Mailer: Rohrpost Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-Spam-Status: No (score 0.3): AWL=0.308 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Wed, 02 May 2007 10:32:55 -0500 X-archive-position: 1616 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: 20h@r-36.net 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 Good day. Am Wed, 2 May 2007 05:40:04 -0700 (PDT) schrieb Cameron Kaiser : > > I am not running a gopherd on r-36.net because of the lack of > > features in Gopher. > > I'm sorry, this is a terribly ironic statement. Most of us are running > Gopher to *avoid*: But I need a way to address only a certain range of bytes in a file, to get the size of the to be downloaded file and to see if the file was changed since I last got it. Of course Gopher has the advantage of a defined directory index, but you can assume this in HTML (without Java- script) too. > simply because such features are weighty or unnecessary for the > purpose of using a gopher server. It also detracts from the > practicality of server software if you are, so to speak, unwilling to > "eat your own dog food." If you won't run it, why would anyone else? Noone is supposed to run the gopherd. It was written for Plan 9 so it got some way to be integrated into the gopherspace and because the protocol is easy to implement. The port of that gopherd to Linux/BSD was just a fun project. And the current feature change was done so I can use the gopherfs for simple and fast to setup file transfer. > For many people running a gopher server alone is unrealistic, and I > don't offer all my services on gopher, but rather pick the ones that > are appropriate for each. That is too much effort in a pure standard Apache environment and it opens another port. If you can do it over HTTP, why would you do it over Gopher? I am sorry, I am not a gopher enthusiast. Sincerely, Christoph Lohmann