The Service Provider Interface (SPI)
for the CertStore class. All CertStore
implementations must include a class (the SPI class) that extends
this class (CertStoreSpi), provides a constructor with
a single argument of type CertStoreParameters, and implements
all of its methods. In general, instances of this class should only be
accessed through the CertStore class.
For details, see the Java Cryptography Architecture.
Concurrent Access
The public methods of all CertStoreSpi objects must be
thread-safe. That is, multiple threads may concurrently invoke these
methods on a single CertStoreSpi object (or more than one)
with no ill effects. This allows a CertPathBuilder to search
for a CRL while simultaneously searching for further certificates, for
instance.
Simple CertStoreSpi implementations will probably ensure
thread safety by adding a synchronized keyword to their
engineGetCertificates and engineGetCRLs methods.
More sophisticated ones may allow truly concurrent access.
CertStoreimplementations must include a class (the SPI class) that extends this class (CertStoreSpi), provides a constructor with a single argument of typeCertStoreParameters, and implements all of its methods. In general, instances of this class should only be accessed through theCertStoreclass. For details, see the Java Cryptography Architecture.Concurrent Access
The public methods of all
CertStoreSpiobjects must be thread-safe. That is, multiple threads may concurrently invoke these methods on a singleCertStoreSpiobject (or more than one) with no ill effects. This allows aCertPathBuilderto search for a CRL while simultaneously searching for further certificates, for instance.Simple
CertStoreSpiimplementations will probably ensure thread safety by adding asynchronizedkeyword to theirengineGetCertificatesandengineGetCRLsmethods. More sophisticated ones may allow truly concurrent access.