Service provider interface (SPI) is an API intended to be implemented or extended by a third party. It can be used to enable framework extension and replaceable components.[1][2][3]

Details

From Java documentation:

A service is a well-known set of interfaces and (usually abstract) classes. A service provider is a specific implementation of a service. The classes in a provider typically implement the interfaces and subclass the classes defined in the service itself. Service providers can be installed in an implementation of the Java platform in the form of extensions, that is, jar files placed into any of the usual extension directories. Providers can also be made available by adding them to the application's class path or by some other platform-specific means.[4]

The concept can be extended to other platforms using the corresponding tools. In the Java Runtime Environment, SPIs are used in:[1][2]

See also

References

  1. 1 2 "Introduction to the Service Provider Interfaces". Oracle Java Documentation. Services are units of sound-handling functionality that are automatically available when an application program makes use of an implementation of the Java Sound API
  2. 1 2 Thribhuvan Thakur (November 18, 2009). "Service Provider Interface: Creating Extensible Java Applications". Developer.com. A service provider interface (SPI) is the set of public interfaces and abstract classes that a service defines. A SPI may be represented by a single interface (type) or abstract class or a set of interfaces or abstract classes that define the service contract.
  3. ↑ Seacord, C. Robert & Wrage, Lutz (July 2002). "Replaceable Components and the Service Provider Interface". Software Engineering Institute (CMU).
  4. ↑ "ServiceLoader".
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.