From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263628AbTJWPNP (ORCPT ); Thu, 23 Oct 2003 11:13:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263637AbTJWPNP (ORCPT ); Thu, 23 Oct 2003 11:13:15 -0400 Received: from modemcable137.219-201-24.mtl.mc.videotron.ca ([24.201.219.137]:47744 "EHLO montezuma.fsmlabs.com") by vger.kernel.org with ESMTP id S263628AbTJWPNN (ORCPT ); Thu, 23 Oct 2003 11:13:13 -0400 Date: Thu, 23 Oct 2003 11:12:47 -0400 (EDT) From: Zwane Mwaikambo To: John Bradford cc: linux-kernel@vger.kernel.org Subject: Re: In-kernel Gopher server In-Reply-To: <200310231501.h9NF164o006515@81-2-122-30.bradfords.org.uk> Message-ID: References: <200310230930.h9N9U0B4006046@81-2-122-30.bradfords.org.uk> <200310231501.h9NF164o006515@81-2-122-30.bradfords.org.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 23 Oct 2003, John Bradford wrote: > Maybe the wristwatch example was a bit extreme, but what about a > system with very low bandwidth for connectivity? What if you were > trying to get configuration data back from a spacecraft millions of > miles away? At 300 BPS or less, and hours of latency, Gopher starts > to look a bit more realistic than getting a shell prompt via ssh :-). Ok so i've missed the point as to why we need it in the kernel.