Sean,
Would a SecurityManager and Policy provider combination that has no
perceptable impact on performance and is highly scalable qualify?
It's a drop in fully compatible replacement.
Regards,
Peter.
Original Message
Subject:Re: Concurrent Policy provider
Date:
Maybe you already know this, but this past April, Sean Mullan (from
Oracle) posted a "JEP Review Request" [1] for a blanket initiative to
improve security manager performance.
This kind of thing sounds like exactly the sort of thing that would fit
in under that initiative, IMO.
[1]
http://m
Would there be interest in using a Policy provider and SecurityManager
designed for concurrency in Java 9?
Some of the issues experienced and solutions are mentioned below.
http://svn.apache.org/viewvc/river/jtsk/skunk/qa_refactor/trunk/src/org/apache/river/api/security/
Regards,
Peter.
Looks fine to me.
Xuelei
On 7/11/2014 8:41 AM, Wang Weijun wrote:
> Please review the code change at
>
>http://cr.openjdk.java.net/~weijun/8049936/webrev.00/
>
> blacklisted.certs.pem was moved from src/ to make/ in JDK-8047765. The test
> should also be updated.
>
> Thanks
> Max
>
Please review the code change at
http://cr.openjdk.java.net/~weijun/8049936/webrev.00/
blacklisted.certs.pem was moved from src/ to make/ in JDK-8047765. The test
should also be updated.
Thanks
Max
Hi All
Please review the code change at
http://cr.openjdk.java.net/~weijun/8049834/webrev.00/
These 2 tests do not run with only JRE because they are testing on jarsigner.
The weaksize.sh is simply moved to jarsigner, and default_options.sh broken
into 2 parts with the jarsigner part going t
