1996-04-30 - Re: Calling other code in Java applications and applets

Header Data

From: Andrew Purshottam <woutput@earthlink.net>
To: “Timothy C. May” <tcmay@got.net>
Message Hash: 46417964b2bfb856d5aada80f948cb209ae351f63295e24345acd32dd8155d54
Message ID: <31856BCD.463A@earthlink.net>
Reply To: <adaadb06040210042638@[205.199.118.202]>
UTC Datetime: 1996-04-30 17:29:35 UTC
Raw Date: Wed, 1 May 1996 01:29:35 +0800

Raw message

From: Andrew Purshottam <woutput@earthlink.net>
Date: Wed, 1 May 1996 01:29:35 +0800
To: "Timothy C. May" <tcmay@got.net>
Subject: Re: Calling other code in Java applications and applets
In-Reply-To: <adaadb06040210042638@[205.199.118.202]>
Message-ID: <31856BCD.463A@earthlink.net>
MIME-Version: 1.0
Content-Type: text/plain


> 
> And I believe that even applets can read and write data files on disk IF
> THE APPLET ENVIRONMENT PERMITS this. Netscape and similar environments at
> this time of course _don't_ let this happen, but this is a choice (as I
> understand it) made at this time and perhaps for this version of the
> respective pieces of software. (As I understand it, an explicit decision
> not to allow file i/o, for some obvious though not necessarily permanent
> reasons.)
This is correct. A class called the SecurityManager enforces this,
and it can be changed or shut off if one builds a custom version of the
classes zip file that has the appropriate changes to the security manager.
There was a posting to a java news group or mailing list about how to do
this a few months ago, I can find it if anyone cares.

Andy





Thread