7 Commits

Author	SHA1	Message	Date
Alex Dadgar	c19cd2e5cf	loader and singleton	2019-01-22 15:11:57 -08:00
Nick Ethier	1ff3b681da	drivermanager: use correct plugin config types	2018-12-18 23:07:01 -05:00
Nick Ethier	12528cadda	drivermanager: attempt to reattach and shutdown driver plugin if blocked by allow/block lists	2018-12-18 23:01:57 -05:00
Nick Ethier	6951ca487d	drivermanager: use allocID and task name to route task events	2018-12-18 23:01:51 -05:00
Nick Ethier	3100f7bd64	client/pluginmanager: add plugin manager interface to device/driver managers	2018-12-18 22:56:23 -05:00
Nick Ethier	2f010a2f25	client/drivermananger: fixup issues from rebase and address PR comments	2018-12-18 22:55:38 -05:00
Nick Ethier	39ca1b00dd	client/drivermananger: add driver manager ... The driver manager is modeled after the device manager and is started by the client. It's responsible for handling driver lifecycle and reattachment state, as well as processing the incomming fingerprint and task events from each driver. The mananger exposes a method for registering event handlers for task events that is used by the task runner to update the server when a task has been updated with an event. Since driver fingerprinting has been implemented by the driver manager, it is no longer needed in the fingerprint mananger and has been removed.	2018-12-18 22:55:18 -05:00