core

Namespace for package core

Types

Name	Description
BaseWorker	WorkerBase class contains one queue: request and can start auxiliary thread that will run on opposite end of the queue: Main thread Queue Auxiliary thread Methods push(...) --> request --> receive(...)
Device	@brief all Karabo devices derive from this class The Device class is the base class for all Karabo devices.
DeviceClient	@brief This class can be used to (remotely) control devices of the distributed system Synchronous calls (i.e. get()) are in fact asynchronous under the hood The Karabo DeviceClient provides a high-level interface for common calls to (remote) devices in the distributed system. In principle functionality implemented in the DeviceClient can be fully implemented in the Device using low level SignalSlotable calls alone, but device developers are discouraged from this approach, especially if synchronous behavior is acceptable or even desired. In the context of a Device the DeviceClient is available using the Device::remote() function; it then shares the SignalSlotable instance of the device, e.g. there is no instantiation overhead.
DeviceServer	@brief The DeviceServer class hosts device instances The DeviceServer class hosts device instances.
InstanceChangeThrottler	@brief Receives instance new, update and gone messages and dispatches them to an interested part in "cycles" spaced by a given interval.
Lock
Runner	@brief The Runner class starts device-servers in the distributed system The Runner class instantiates device-servers in the distributed system.
Worker	A worker that passes any data received in its queue to a callback function working asynchronously working in a separate thread.