Re: External behaviors (was Re: MISC: Inlined Sound Support)

Brian Behlendorf ([email protected])
Tue, 18 Apr 1995 17:36:45 -0800 (PST)


On Tue, 18 Apr 1995, Kevin Goldsmith wrote:
> > Yes, this is the crux of the issue. We don't really need to specify
> > anything about the scripting language itself, it's the binding that
> > is important. And as you alluded to before, this "binding" should be the
>
> Explain this to me. I write my script in Cobra, you write yours
> in C, someone else writes theirs in Prolog. How are all these different
> scripts supposed to be executed by the browsers?

http://java.sun.com/. The only kinds of Turing-complete languages which
will be allowed are those which can be analyzed by the browser to ensure
they run in a safe "virtual machine".

> API aside. Let's say
> we define an API, well then when I write a script and then "compile" it
> for Windows, Mac, SGI, SUN, etc... Am I missing something here?

Obviously the language will have to be platform dependent, and preferably
the compilation happens in the browser itself after the code has
been fetched (this makes safety checking not a herculean task, too).
Java and Safe-Tcl are both platform-independent - heck, even Perl's
pretty independent these days too, though hardly secure.

Brian