Re: Interactive HTML (revised)

869683 Gillespie Brandon James (brandon@avon.declab.usu.edu)
Mon, 23 Oct 1995 22:27:28 -0600


Date: Mon, 23 Oct 1995 22:27:28 -0600
From: 869683 Gillespie Brandon James <brandon@avon.declab.usu.edu>
Message-Id: <9510240427.AA04840@avon.declab.usu.edu>
To: www-html@w3.org
Subject: Re: Interactive HTML (revised)

This sounds like a pretty standard gateway problem to me. Does it even
< need it's own scheme? Why not:

Read the original post, iHTML is interactive, totally different from the
way html is currently handled (static documents).  There are no 'gateways'
involved because you are basically at the equivalent of a shell login.
Using this example (as simply an example, this is not actually the intended
use (so no comments about just using emacs please ;)) you could get a
directory listing by typing 'ls -lF'.  Except for your 'terminal' (i.e.
client) is "ihtml" aware, so rather than flat text you see something
like:

-rw-r--r--   1 brandon      1006 Sep 14 15:50 <a href="local:less cgi.pl">cgi.pl</a>
drwxr-xr-x  15 brandon       512 Oct  3 02:13 <a href="local:cd bin">bin/</a>

etc.  Basically you are defining something which can have an action
envoked upon it, and the action is simply returned in the interactive
login you have (regurgitated).  The whole setup is very basic, and
almost seems not worth the effort, until you start considering some
of the greater usages available.  For instance, you can anchor anywhere,
not just on the local interactive login--help documents (man pages) can
start locally and move off-system transparently.

Once again, I reiterate, the above example is not the intended use,
although it could be used as such :)

-Brandon Gillespie-