[698] in java-interest
Re: java-interest-digest V1 #82
daemon@ATHENA.MIT.EDU (Chris Warth)
Thu Jul 13 19:22:45 1995
Date: Thu, 13 Jul 1995 15:15:46 -0700
From: csw@scndprsn.Eng.Sun.COM (Chris Warth)
To: ekim@nyquist.bellcore.com
Cc: java-interest@java.Eng.Sun.COM
> Is this what is called a "fat binary". Multiple versions of a class
> or a method which have the right binary version picked at runtime?
>
In principle, yes, this would be a fat binary, but I doubt that we will
ship around class files with a bunch of different machine code versions
in them. All I intended to point out is that the class file format can
*potentially* handle multiple architectures. We intend to do on the
fly compilation to machine code at runtime as the white paper said.
> I have no expertise in security - but if the class has binary code then
> does this cause a security problem because Java cannot verify the code?
>
Absolutly. Theoretically I suppose you could checksum and sign the
compiled code, but it's not worth it. Just do on the flay
compilation. You verify the bytecodes and then compile them top
machine code. Shipping machine code across the wire is a losing
proposition.
-csw
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
