[JOS-Kernel] Re: Processenvironment, was: "Re: [JOS-Arch] RE: [JOS-UI]peer-ui mappings" peer-ui mappings"

[Gilbert Carl Herschberger II]

At 12:12 PM 7/22/99 +0000, Mark Andreas Meyer <[EMAIL PROTECTED]> wrote:

<snip>

>What do you think about the following concept?
>
>We'll use a standard vm that provides everything jos needs (basically
hardware
>access), on top of this processes will be executed in a ProcessEnvironment,
>that uses jos.vm.<impl> to execute bytecode in a protected environment.
jos.vm
>provides a generic interface for executing bytecode that is controlled by
>ProcessEnvironment (ie. you create a new ProcessEnvironment and then
customize
>its "transparency" and customize Factorys to create certain objects
(nobody in
>the ProcessEnvironment will know, what is going on)).

I like the idea of using a standard vm, for now. It already has native
hooks into my current operating system services. At first, I thought we
could build something using System.in; but, System.in is too limited.
Recently, I'm settled on the idea that we need to simulate the keyboard
through a TCP/IP connection, like telnet. We could interact naturally with
a JOS service running inside a standard JVM. We could get around the
problem of System.in, System.out and System.err. We could do the multiple
process thing, with process environment.

Also, I think we can use this environment to build JOS-compatible
applications now, even before the rest of this is ready. Why not start with
a single TCP/IP connection, supplied by an off-the-shelf JVM, and build up
from there?

Such a JVM service would need device drivers and separate threads. Running
under javaw or jrew, JOS-compatible applications can open additional
windows, dialog boxes, and such.

>jos.vm will satisfy our needs as a vm with lots of features at a lightening
>speed and controlled by ProcessEnvironment we can build customized
>(=downgraded to Suns Java) and really safe SubVMs. Imagine: Jos supports J3
>before Suns beta test finishes. Additionaly the concept can be extended to
>include hardware accelerators and other VMs (ie. Smalltalk ).

When JOS supports Java 3.0 even before Sun, this will put JOS and open
source on the map. I see that JOS has the potential to be THE KILLER APP
for Java. JOS is something you can't do on any other platform.

>Waiting for the enlightenment in the form of your comments, Mark :)

What a nice thing to say. When I get to the end of an e-mail,



_______________________________________________
Kernel maillist  -  [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel