PROPOSAL: "W3A" - a client-side applets API
Bert Bos <bert@let.rug.nl>
Errors-To: listmaster@www0.cern.ch
Date: Fri, 24 Jun 1994 14:19:45 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <9406241216.AA27426@freya.let.rug.nl>
Errors-To: listmaster@www0.cern.ch
Reply-To: bert@let.rug.nl
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Bert Bos <bert@let.rug.nl>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: PROPOSAL: "W3A" - a client-side applets API
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: text/plain; charset=US-ASCII
Content-Type: text/plain; charset=US-ASCII
Mime-Version: 1.0
Mime-Version: 1.0
X-Mailer: ELM [version 2.4 PL23]
X-Mailer: ELM [version 2.4 PL23]
After several false starts, including forays into FIFOs, TCP, and X
events, I have finally found a model for WWW `accessories' that looks
simple, yet powerful.
The current state of my ideas can be found at
<http://www.let.rug.nl/~bert/W3A>
Briefly:
It is an interface (API) between a WWW browser and `applets' which can
implement protocols, conversions, viewers, hotlists, and other
utilities. It is based on dynamic linking and a stream model (open,
read/write, close).
A browser must export 12 functions. An applet must export 2-7
functions, depending on its type.
Preliminary results show that a minimal browser (without a GUI of its
own) can be written in less than 400 lines, including the code for
dynamic linking. An applet for the Gopher or the HTTP protocol (sans
cryptography) takes about 200 lines.
Could this be the key to unleashing the myriads of ideas about viewers
and accessories that people have, but until now couldn't implement...?
Reactions, please!
--
__________________________________
/ _ Bert Bos <bert@let.rug.nl> |
() |/ \ Alfa-informatica, |
\ |\_/ Rijksuniversiteit Groningen |
\_____/| Postbus 716 |
| 9700 AS GRONINGEN |
| Nederland |
| http://tyr.let.rug.nl/~bert/ |
\__________________________________|