Received: with ECARTIS (v1.0.0; list gopher); Thu, 05 Jan 2006 18:28:38 -0600 (CST) Received: from outbound3.mail.tds.net ([216.170.230.93]) by glockenspiel.complete.org with esmtp (Exim 4.50) id 1EufT9-0001pA-0Q for gopher@complete.org; Thu, 05 Jan 2006 18:28:38 -0600 Received: from outaamta01.mail.tds.net (outaamta01.mail.tds.net [216.170.230.31]) by outbound3.mail.tds.net (8.13.4/8.12.2) with ESMTP id k060SS5Y027167 for ; Thu, 5 Jan 2006 18:28:28 -0600 (CST) Received: from wybotnnas01-pool0-a130.wybotn.tds.net ([66.222.116.130]) by outaamta01.mail.tds.net with ESMTP id <20060106002827.WYLA29906.outaamta01.mail.tds.net@wybotnnas01-pool0-a130.wybotn.tds.net> for ; Thu, 5 Jan 2006 18:28:27 -0600 Date: Thu, 05 Jan 2006 18:28:40 -0600 To: gopher@complete.org Subject: [gopher] Re: Need for protocol changey References: <20060104230913.GA28833@SDF.LONESTAR.ORG> <20060105231955.GA27530@SDF.LONESTAR.ORG> From: Jeff Content-type: text/plain; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20060105231955.GA27530@SDF.LONESTAR.ORG> User-Agent: Opera M2/8.51 (Win32, build 7712) X-Spam-Status: No (score 0.1): AWL=0.066 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Thu, 05 Jan 2006 18:28:38 -0600 X-archive-position: 1239 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: geph@nerdshack.com 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 On Thu, 05 Jan 2006 17:19:55 -0600, Benn Newman wrote: > You say there are failings of Gopher+, okay, fine. But what are we > actually > trying to do by making changes to the protocol. How does Gopher benefit > from having MIME types being so integrated? As John pointed out > a Tar-gziped file could have any of number of MIME types but you can > always use extensions. I know that .tar.gz or .tgz means a gziped-tar > file. Without MIME, you're just downloading a 9/Binary file, which may or may not have had a tgz 'extension' in the selector. As Mr. Goerzen wrote, "IE sometimes looks at the extension of a file to determine what sort of file it is, and this is generally considered a bug." > If I want to know a file size, there are perfectly good ways to do so in > Gopher+ > and in Gopher even. File sizes can be a part of the selectors info text > ex: 0Super cool book (book.tgz 4kb)\tboot.tgz\tumn.edu\t7070 There is no standard way to show filesize in gopher. I don't think tacking some stuff in parenthesis to the end of the display string and expecting a client to read it as file data is such a good idea. > Feel free to convince me that protocol changes are needed, I haven't > stopped listening yet. *grin* The fact that the foremost gopher/gopher+ developers were interested in changing the protocol isn't enough? -- Jeff