To: gopher@complete.org
Subject: [gopher] Re: PyGopherd 2.0 released; Gopher and WAP
References: <920eb7ee00368cade31e1aa13695a2e6@Bouncing>
Message-ID: <oprumci2e1oh6hmd@localhost>
Content-type: text/plain; charset=iso-8859-15
From: PapaLazarus <papalazarus@f2s.com>
MIME-Version: 1.0
Date: Thu, 28 Aug 2003 15:14:52 +0100
In-Reply-To: <920eb7ee00368cade31e1aa13695a2e6@Bouncing>
User-Agent: Opera7.10/Win32 M2 build 2840
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

On 2003-08-26 20:59:13 +0100 PapaLazarus wrote:
>> [...] charged by time not packets, making it cheaper to use a graphic 
>> intensive
>> page then a gopher page.

On Thu, 28 Aug 2003 00:35:50 +0100, MJ Ray wrote:
> How is downloading a lot of graphics going to be cheaper than a few 
> gopher menus?

A pictures worth a thousand words, well maps & diagrams. A set amount of
information can be processed by the user quicker if relevent images are
used compared to plain text. The faster the information can be processed
the smaller the phone bill.
It the billing was based on data, not time, a text dased system would be
preferable. Directions could be brought up on a phone then left on the
phone till the user had finished following them.


-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/