RFR 7004967: SecureRandom should be more explicit about threading

[Xuelei Fan]

On 11/2/2016 9:33 PM, Wang Weijun wrote:
>> >>>
>> >>> 1.  More specific
>> >>>
>> >>>  "A SecureRandom service provider can advertise that it is
>> >>>   thread-safe by setting the service provider attribute
>> >>>   "ThreadSafe" to "true" when registering the provider."
>> >>>
>> >>> A service provider may contains many services implementations.  May need to be more specific to set "ThreadSafe" for SecureRandom only, rather the full provider is thread safe.  For example:
>> >>>
>> >>>   map.put("SecureRandom.SHA1PRNG ThreadSafe", "true");
>> >>>
>> >>> Otherwise, a service provider need to make sure all services are thread safe, or all services implementation are not thread safe.
>>>
>>> How about changing "A SecureRandom service provider" to "A SecureRandom implementation"?

I may change "the service provider attribute" to "the service attribute".

    A SecureRandom service provider can advertise that the
    implementation is thread-safe by setting the service attribute
    "ThreadSafe" to "true" when registering the provider.

Xuelei