ActiveScript is the term used to describe a set of COM interfaces that permit a scripting language interpreter to be used by a scripting site or client. The interfaces provide an abstraction mechanism such that an ActiveScript client need not know or care what language is being used. This means that the user of such an application can use Perl if she so chooses rather than VBScript and the client application doesn't need to be changed.
[Provide relevant URLs to define and further discuss this area]
An Active Script engine exposes a scripting language interpreter through the Active Script interfaces. Two Tcl Active Script engine prototypes exist, as of spring 2002: Tclscript and tcom 3.8 and above.
IIS, Internet Explorer and Windows Script Host [L1 ] are examples of applications that host Active Script engines through the Active Script interfaces.
IIS might be able to interpret this ASP:
<%@ LANGUAGE = "TclScript" %>
<%
Response Write "Hello world!"
%>In Internet Explorer:
<html>
<head>
<title>TclScript Test</title>
<script language="TclScript">
proc setText {newValue} {
text1 value $newValue
}
</script>
</head>
<body>
<input id="text1" name="text1" disabled="1">
<p>
<input type="button" id="button1" name="button1" value="Hello"
onclick="setText hello">
<input type="button" id="button2" name="button2" value="World"
onclick="setText world">
</body>
</html>In Windows Script Host:
WScript Echo "Hello world!"