To: gopher@complete.org
Subject: [gopher] Re: Heads up
References: <873d1go1pb.fsf@complete.org>
	<20020108215303.A10851@mothra.dyndns.org>
	<87bsg0q50w.fsf@complete.org>
	<E16P5bm-0000JS-00@cloaked.freeserve.co.uk>
	<876668oixp.fsf@complete.org>
	<E16P8VC-0000M0-00@cloaked.freeserve.co.uk>
From: John Goerzen <jgoerzen@complete.org>
Date: Fri, 11 Jan 2002 15:58:55 -0500
In-Reply-To: <E16P8VC-0000M0-00@cloaked.freeserve.co.uk> (MJ Ray's message
 of "Fri, 11 Jan 2002 20:42:14 +0000")
Message-ID: <878zb461v4.fsf@complete.org>
Lines: 20
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Common Lisp)
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


MJ Ray <markj@cloaked.freeserve.co.uk> writes:

> Sorry, I was mixing two concepts in one email.  Is interactivity (user
> input displays, etc) possible with gopher, or does it require gopher+?

I believe it is possible in a very limited fashion with gopher0 but
that ASK blocks and the like require gopher+.

In practice, I believe that for most things that you might consider
interactivity in gopher for, you might prefer HTTP and CGI.

Incidentally: there may be other ways to do interactivity than this sort of input.

For instance, maybe you want a gopher to NNTP gateway.  You could
write a simple gopher server that listens on a high port.  It could
generate all its content on the fly based on conversations with the
NNTP backend somewhere -- the gopher "directories" could be listings
of groups, or messages in the groups.

-- John