Received: with LISTAR (v1.0.0; list gopher); Fri, 15 Jun 2001 11:35:49 -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 72C483B80B for ; Fri, 15 Jun 2001 11:35:49 -0500 (EST) Received: (from spectre@localhost) by stockholm.ptloma.edu (8.9.1/8.9.1) id JAA10528 for gopher@complete.org; Fri, 15 Jun 2001 09:39:01 -0700 From: Cameron Kaiser Message-Id: <200106151639.JAA10528@stockholm.ptloma.edu> Subject: [gopher] Re: Getting file info from an URI?? In-Reply-To: <992619438.769.0.camel@Pflipp> from Stefan Rieken at "Jun 15, 1 05:37:17 pm" To: gopher@complete.org Date: Fri, 15 Jun 2001 09:39:01 -0700 (PDT) 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: 180 X-listar-version: Listar 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: Listar version 1.0.0 X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher > > Well, this isn't *really* true. The first character is always the item type. > > Well, that may be common current practice, but that's not quite required > behaviour from either the Gopher or the Gopher+-standards, is it? > > If so, determining the file type by looking at the first character may > now work in 99% of the cases, until someone develops a "new, improved" > Gopher server which uses different selectors that gets popular, after > which maybe only in 70% of the cases this will work.