Received: with ECARTIS (v1.0.0; list gopher); Mon, 02 Jan 2006 09:01:35 -0600 (CST) Received: from ol.freeshell.org ([192.94.73.20] helo=sdf.lonestar.org) by glockenspiel.complete.org with esmtp (Exim 4.50) id 1EtRBl-0002yH-3c for gopher@complete.org; Mon, 02 Jan 2006 09:01:35 -0600 Received: from sdf.lonestar.org (IDENT:newmanbe@iceland.freeshell.org [192.94.73.5]) by sdf.lonestar.org (8.13.1/8.12.10) with ESMTP id k02F1IgQ000248 for ; Mon, 2 Jan 2006 15:01:19 GMT Received: (from newmanbe@localhost) by sdf.lonestar.org (8.13.1/8.12.8/Submit) id k02F1Ikg003325 for gopher@complete.org; Mon, 2 Jan 2006 09:01:18 -0600 (CST) Date: Mon, 2 Jan 2006 09:01:18 -0600 From: Benn Newman To: gopher@complete.org Subject: [gopher] Re: PyGopherd and Gopher+ Message-ID: <20060102150118.GA7431@SDF.LONESTAR.ORG> References: <20051231155642.GA9489@SDF.LONESTAR.ORG> <20051231164643.GB28740@katherina.lan.complete.org> <20051231173023.GA2684@SDF.LONESTAR.ORG> <20060101165144.GA2143@SDF.LONESTAR.ORG> Mime-Version: 1.0 Content-type: text/plain Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Spam-Status: No (score 0.2): AWL=0.116, FORGED_RCVD_HELO=0.05 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Mon, 02 Jan 2006 09:01:35 -0600 Content-Transfer-Encoding: 8bit X-archive-position: 1218 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: newmanbe@sdf.lonestar.org 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 Mon, Jan 02, 2006 at 03:01:41AM -0600, Jeff wrote: > On Sun, 01 Jan 2006 10:51:44 -0600, Benn Newman > Here are a few of my ideas: > > 1) As I wrote in my previous post, I think that reserving new tabspaces > for information like mimetype and filesize would be a good start. The > file's last-modified date would also be nice. > A menu would look similar to this, > > "1This points to a gopher > menu%09/selector%09host%09port%09size%09mimetype". > Where %09 is a hex-encoded tab. The nice thing abous Gopher+ blocks is that they can hold arbitrary information. Do we want to limit ourselves like this? Something we might want to keep in mind from the GopherCON 1994 State of the Gopher: 1992: Growth and Gopher+ [snip] -Limits of the initial protocol become apparent Needed a place to store meta-information Administrator Electronic forms Alternate data formats (views) Modification date Abstract -- Benn Newman | newmanbe@sdf.lonestar.org | gopher://igneous-rock.homeunix.net Wisconsin Association of Gopher Operators Learn about the Gopher Project: http://gopher.quux.org/Software/Gopher -- Attached file included as plaintext by Ecartis -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (NetBSD) iEYEARECAAYFAkO5QD4ACgkQFE65lPR8xrGu3gCeMtFoEgBiZL3KRzzGKFOHdgrF imsAnj8zvIUNYZk0UTSD/wJeVzYcIeZT =OWqD -----END PGP SIGNATURE-----