Received: with ECARTIS (v1.0.0; list gopher); Thu, 28 Aug 2003 09:35:42 -0500 (CDT) Return-Path: <mjr@towers.org.uk> X-Original-To: gopher@complete.org Delivered-To: gopher@complete.org Received: from localhost (localhost [127.0.0.1]) by gesundheit.complete.org (Postfix) with ESMTP id 085E918320C0 for <gopher@complete.org>; Thu, 28 Aug 2003 09:35:42 -0500 (CDT) Received: from pengo.systems.pipex.net (pengo.systems.pipex.net [62.241.160.193]) by gesundheit.complete.org (Postfix) with ESMTP id 43B4518320B5 for <gopher@complete.org>; Thu, 28 Aug 2003 09:35:41 -0500 (CDT) Received: from me (81-86-163-141.dsl.pipex.com [81.86.163.141]) by pengo.systems.pipex.net (Postfix) with SMTP id 46CC34C004EA for <gopher@complete.org>; Thu, 28 Aug 2003 15:35:35 +0100 (BST) Received: (nullmailer pid 932 invoked by uid 1000); Thu, 28 Aug 2003 14:37:05 -0000 Date: Thu, 28 Aug 2003 15:37:04 +0100 Subject: [gopher] Re: PyGopherd 2.0 released; Gopher and WAP Message-ID: <317e848112f34d7f185bcf056962c88d@Bouncing> MIME-Version: 1.0 (Generated by Pantomime 1.1.0) From: MJ Ray <markj@cloaked.freeserve.co.uk> To: gopher@complete.org Organization: My own In-Reply-To: <oprumci2e1oh6hmd@localhost> X-Mailer: GNUMail.app (Version 1.1.0) Content-type: text/plain; charset=us-ascii X-Scanned-By: clamscan at complete.org Content-Transfer-Encoding: 8bit X-archive-position: 811 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: markj@cloaked.freeserve.co.uk Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-Id: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher On 2003-08-28 15:14:52 +0100 PapaLazarus <papalazarus@f2s.com> wrote: > A pictures worth a thousand words, well maps & diagrams. I agree entirely, but nothing prevents a mobile gopher client displaying (or more likely storing for later display, in my case) images. I expect such images would be more relevant to the task than 95% of web images. It also helps navigation speed to have a consistent user interface, such as gopher menus, and not to have to process dense markup. I think gopher probably will come out ahead on access speed for most tasks usually done on mobiles, from combining lots of reasons. As has been said, there's quite a few similar solutions in WAP interfaces as gopher ones. -- MJR/slef My Opinion Only and possibly not of any group I know.