Received: with ECARTIS (v1.0.0; list gopher); Wed, 20 Mar 2002 21:19:23 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from stockholm.ptloma.edu (stockholm.ptloma.edu [199.106.86.50]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 6C0D73B81F for ; Wed, 20 Mar 2002 21:19:23 -0500 (EST) Received: (from spectre@localhost) by stockholm.ptloma.edu (8.9.1/8.9.1) id SAA24810 for gopher@complete.org; Wed, 20 Mar 2002 18:24:15 -0800 From: Cameron Kaiser Message-Id: <200203210224.SAA24810@stockholm.ptloma.edu> Subject: [gopher] Re: \n.\n In-Reply-To: from Thomas Thurman at "Mar 20, 2 09:27:55 pm" To: gopher@complete.org Date: Wed, 20 Mar 2002 18:24:15 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-archive-position: 523 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: spectre@stockholm.ptloma.edu 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 > I think if you're serving files that contain \n.\n, you have trouble > anyway. Isn't it quite within the original spec for a client to stop > reading at that point? It is indeed. I may make getting rid of this a configure time option in bucktooth to force the point. -- ----------------------------- personal page: http://www.armory.com/~spectre/ -- Cameron Kaiser, Point Loma Nazarene University * ckaiser@stockholm.ptloma.edu -- Had this been an actual emergency, we would have fled already. -------------