You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.
when external ScheduledExecutorService was passed - Pi4J should not shutdown it on it's own shutdown (because this resource is managed by somebody, somewhere else).
when Pi4J internal ScheduledExecutorService is provided to external world (for example by GpioController.getScheduledExecutorService) is should not allow to be shuted down by anybody else than Pi4J (this can be done by returning ScheduledExecutorService inside wrapper - ScheduledExecutorServiceWrapper - where shutdown() and shutdownNow() throws UnsupportedOperationException)
Added support for this feature in the latest 0.0.5-SNAPSHOT (2013-02-09) build.
There is a new ExecutorServiceFactory implementation that allow users to provide their own executor service factory where you users can create the executors and manage own thread pool. Users can assign their own ExecutorServiceFactory implementation via the GpioController.
Add ability to pass external executor service
(for example: it can be done by passing ScheduledExecutorServiceFactory to GpioFactory).
There also should me method like GpioController.getScheduledExecutorService if someone would use already created thread pool.
The text was updated successfully, but these errors were encountered: