Received: with ECARTIS (v1.0.0; list gopher); Thu, 18 Mar 2004 05:22:42 -0600 (CST) Return-Path: X-Original-To: gopher@complete.org Delivered-To: gopher@complete.org Received: from localhost (localhost [127.0.0.1]) by glockenspiel.complete.org (Postfix) with ESMTP id C860D3AF for ; Thu, 18 Mar 2004 05:22:38 -0600 (CST) Received: from glockenspiel.complete.org ([127.0.0.1]) by localhost (glockenspiel [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id 32109-08 for ; Thu, 18 Mar 2004 05:22:33 -0600 (CST) Received: from web60207.mail.yahoo.com (web60207.mail.yahoo.com [216.109.118.102]) by glockenspiel.complete.org (Postfix) with SMTP id B020C150 for ; Thu, 18 Mar 2004 05:22:32 -0600 (CST) Message-ID: <20040318112229.93628.qmail@web60207.mail.yahoo.com> Received: from [172.139.70.213] by web60207.mail.yahoo.com via HTTP; Thu, 18 Mar 2004 03:22:29 PST Date: Thu, 18 Mar 2004 03:22:29 -0800 (PST) From: "William G. Davis" Subject: [gopher] Blocks: building and parsing them. To: gopher@complete.org MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at complete.org Content-Transfer-Encoding: 8bit X-archive-position: 905 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: william_gordon_davis@yahoo.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 I came to the conclusion not long ago that Gopher+ attribute information blocks are fundamentally flawed. I realized this when I attempted to write a block parser for Net::Gopher. I figured that—like HTTP headers—they'd be incredibly simple to parse. How about a tree? A hash of block names and values... Maybe a hash of hashes with block names, values, and then attribute names and values within them?