Re: RFC: security policy

On May 2, 2004 12:26 pm, Pat wrote:
> On Sun, May 02, 2004 at 02:31:08AM -0400, Slava Pestov wrote:
> > I think the debug property can be eliminated; if a user wants it set,
> > they can just set the static field. As for user.home, loadRCFiles() is
> > protected with try/catch, so not being able to access this property
> > should not cause any problems, no?
>
> Well, we need a general way to turn it on and off from outside the
> script... Although the debug output is not currently very pretty, it does
> help sometimes when something goes wrong.

From my perspective, I would have a JToggleButton for debug enable/disable - 
which would need to call something like Interpreter.enableDebug(true);

> I think it should just be a matter of catching any security exception and
> ignoring it, shouldn't it?   Or does violating the policy cause instant
> death for some reason?

Catching the Exception is fine :-)

-- 
VoIP SIP:[email protected]
Free calendar client and server - works with Exchange/Outlook/Yahoo!
TV-Listing and Weather Schedules
http://www.ScheduleWorld.com/
http://www.ScheduleWorld.com/sw/ScheduleWorld.jnlp (JWS)


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_id66&op=click