HTTP/1.1 200 OK
Date: Tue, 24 Nov 2009 03:24:31 GMT
Server: Apache/2.2.6 (Fedora)
Last-Modified: Sat, 02 Sep 1995 02:50:01 GMT
ETag: "73cc5-cd1-324b8840"
Accept-Ranges: bytes
Content-Length: 3281
Connection: close
Content-Type: text/html; charset=UTF-8
Reasons PRO
- Vastly more people will exploit client extensibility if it is based on a high-level, interpreted scripting language.
- High-level approach may be more amenable to robust security (external actions meaningful to human targets).
Reasons CON
- High-level approach results in `language wars'.
- Agent security is still a hard problem.
Applications
- Extensible field validation for database apps.
- Custom graphical control widgets for specialized apps.
- Simple interactive animations.
Proposed Solutions
- Safe-Python:
- Tcl:
- Java - see Virtual Machines page.
- Viola scripting language and browser (applets on the Web since 1993!) - Pei Wei
- Phantom (safe, distributed, object-oriented scripting language derived from Modula-3) - Antony Courtney
- SMSL (Standard Multimedia Scripting Language) - ANSI X3V1 Committee
- BEF (object-oriented PASCAL-like scripting language embedded in VRML) - BE Software Company
- High Telescript - apparently: an Object Pascal-like language, supporting concept of suspension and remote resumption of execution, but not currently implemented through mobile code (hmm...); see MagicCap Telescript docs for more info.
- Visual Basic - not officially proposed, but wake up and smell the Starbucks :-)
- ``Client Pull'' (not really scripting, just a simple client-to-server callback) - Netscape
Updated: Fri Sep 1 1995
Up to Client extensibility.
Home to Interactive Standards Home Page.
- 1.
Client-side Scripting without Scripts (Dave Raggett)
- 1. Virtual machines category has been added
(Paul Burchard)