What sort of services are you thinking of adding? Technically, things like a CacheLoader or a SecurityManager are SPIs in the sense that they places where you can plug your code into geode. Using a ServiceLoader might ok in cases where we want something to be plugged in if the jar is on the classpath, without any additional configuration. So it probably depends on what the SPI is for.
-Dan On Tue, Jan 8, 2019 at 3:59 PM Dale Emery <dem...@pivotal.io> wrote: > We are exploring adding one or more public Service Provider Interfaces > (SPIs) for Geode, and would like some guidance about standards, > conventions, precedent, and such. > > Do we have standards or conventions for creating SPIs? Good examples? Bad > examples? > > Are there standards or conventions described elsewhere (e.g. Spring) that > we should consider when defining SPIs? > > Is it as simple(!) as defining a service interface, then using Java's > ServiceLoader mechanism to discover and load instances of it? > > Any additional considerations for adding a public SPI, compared to a > private one? > > Cheers, > Dale > >
