Received: with ECARTIS (v1.0.0; list gopher); Mon, 15 Mar 2004 00:42:12 -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 2F6B9303 for ; Mon, 15 Mar 2004 00:42:10 -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 24582-10 for ; Mon, 15 Mar 2004 00:42:08 -0600 (CST) Received: from web60204.mail.yahoo.com (web60204.mail.yahoo.com [216.109.118.99]) by glockenspiel.complete.org (Postfix) with SMTP id E5A6BCD for ; Mon, 15 Mar 2004 00:42:03 -0600 (CST) Message-ID: <20040315064203.72311.qmail@web60204.mail.yahoo.com> Received: from [172.208.214.177] by web60204.mail.yahoo.com via HTTP; Sun, 14 Mar 2004 22:42:03 PST Date: Sun, 14 Mar 2004 22:42:03 -0800 (PST) From: "William G. Davis" Subject: [gopher] Re: Announcing Gopher::Server 0.1 for Perl To: gopher@complete.org In-Reply-To: <20040314170335.GA64675@wumpus-cave.net> 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: 897 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 --- Timm Murray wrote: > Yes, I have some ideas on a database-driven Gopher > server, where > the physical files would be stored as SHA1 sums on > the filesystem > and the database would point to them. Thanks to the > magic of > relational databases, different file formats can be > easily stored > as the same database row, but that row would relate > to a 'formats' > table that would specify the given MIME/Gopher type > for seperate > files that contain the same information. The whole > idea is to make > good use of +VIEWS. This is all dream-mode stuff at > this point, and > I'll need to implement Gopher+ first. That all sounds very exciting. > Also, thanks for your work on Net::Gopher. Using > some of the > Net::Gopher classes that were already available made > implementing > Gopher::Server a lot easier. The only constructive > critisim I have > is that the Net::Gopher::Response class seemed too > oreinted twards the > client side of things, so Gopher::Server::Response > replicates the > functionality needed to for Response classes for > servers. In the > future, I'd like to see Net::Gopher and > Gopher::Server using the same > Response class. Though ATM, I don't remember what > it was that > convinced me that Net::Gopher::Response wouldn't > work. I'll have to > look over the code and get back to you. Net::Gopher:Response really isn't intended for anything other than client-side response receiving/manipulation, and not response creation. (In fact, the POD doesn't even tell you how to create Net::Gopher::Response objects and populate them, just how to manipulate them.) When I started work on my server, I ended up wanting something like Net::Gopher::Request to store parsed requests... But the namespace "Net::Gopher::Request" is a little to specific. It would be nice to eventually have general purpose, reusable request/response classes (e.g., Gopher::Request and Gopher::Response) like LWP does. __________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com