At 7:45 AM 5/24/96 -0500, Adam Shostack wrote:

Hype about Java and a move to a policy based security mechanism are not incompatible. Perry's security model will probably be NO Java, NO Livescript. Mine might be only Java signed by McAffee can get more than 3 seconds of CPU time, or access remote network ports on the server it came from, no other code can run.

I would like to be able to enforce a policy for Java applet CPU time which says, the applet can have as much time as it wants/needs constrained by: (1) I can always determine how much it is using. (2) I can kill it without killing other processes/threads including the browser. (3) Without interfering with 1 or 2, I can set its priority in relation to other programs running on my machine. In the long term, I would like the ability to sell CPU cycles to Java applets. (Or donate cycles to projects I support.) ------------------------------------------------------------------------ Bill Frantz | The CDA means | Periwinkle -- Computer Consulting (408)356-8506 | lost jobs and | 16345 Englewood Ave. frantz@netcom.com | dead teenagers | Los Gatos, CA 95032, USA