Date: Sun, 7 Jan 2001 18:43:38 -0800
From: emanuel at heatdeath organisation <emanuel@heatdeath.org>
To: gopher@complete.org
Subject: [gopher] Re: An idea
Message-ID: <20010107184338.A31887@success-info.com>
Mail-Followup-To: emanuel at heatdeath organisation <emanuel@heatdeath.org>,
	gopher@complete.org
References: <87itnqsrif.fsf@complete.org>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <87itnqsrif.fsf@complete.org>;
 from jgoerzen@complete.org on Sun, Jan 07, 2001 at 09:32:24PM -0500
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


On Sun, Jan 07, 2001 at 09:32:24PM -0500, John Goerzen wrote:
> Jeff Licquia, one of my coworkers, told me that gopher is suspiciously
> like WAP, which is used on some cellphones that I don't own :-)  He
> suggested a wap-to-gopher gateway along the lines of the heatdeath.org
> web to gopher gateway.  Sound doable?  Useful?  Feasible?

Yes, yes, and yes.  It's part of my plan for webgopher.

Actually gopher is quite different from WAP, more limited in many ways,
but everything you do in gopher (directories, searches, ask blocks)
would map very nicely to WAP.  In fact, using gopher to write a WAP
application would work really well and be simpler than using WML.  How
to display all of gopherspace on a phone is a bit tricky, due to its
very small display (typically 20x4 characters) and limited memory
(typically 1200 bytes).

-- 
emanuel at heatdeath organisation
gopher.heatdeath.org