Re: RFR: 8324646: Avoid Class.forName in SecureRandom constructor [v3]

2024-02-06 Thread Oli Gillespie
On Thu, 1 Feb 2024 10:39:27 GMT, Oli Gillespie wrote: >> Avoid expensive `Class.forName` call when constructing Providers such as >> `SecureRandom` which take constructor parameters. This can easily be cached >> in EngineDescription (this cache already existed before, it was removed in >> [JDK

Re: RFR: 8324646: Avoid Class.forName in SecureRandom constructor [v3]

2024-02-06 Thread Weijun Wang
On Thu, 1 Feb 2024 10:39:27 GMT, Oli Gillespie wrote: >> Avoid expensive `Class.forName` call when constructing Providers such as >> `SecureRandom` which take constructor parameters. This can easily be cached >> in EngineDescription (this cache already existed before, it was removed in >> [JDK

Re: RFR: 8324646: Avoid Class.forName in SecureRandom constructor [v3]

2024-02-06 Thread Aleksey Shipilev
On Thu, 1 Feb 2024 10:39:27 GMT, Oli Gillespie wrote: >> Avoid expensive `Class.forName` call when constructing Providers such as >> `SecureRandom` which take constructor parameters. This can easily be cached >> in EngineDescription (this cache already existed before, it was removed in >> [JDK

Re: RFR: 8324646: Avoid Class.forName in SecureRandom constructor [v3]

2024-02-01 Thread Oli Gillespie
> Avoid expensive `Class.forName` call when constructing Providers such as > `SecureRandom` which take constructor parameters. This can easily be cached > in EngineDescription (this cache already existed before, it was removed in > [JDK-8280970](https://bugs.openjdk.org/browse/JDK-8280970) as un