Signals¶
Signals are the return channel from a thread backend to the frontend (main thread).
The base class is Limef::signal::Signal.
-
namespace signal¶
Signalling threads and filterchains.
Typedefs
-
using SignalClass = std::type_index¶
Identifies the signal subclass.
Backed by
std::type_index, so every concreteSignalsubclass gets a unique identity for free (viaSIGNAL_CLASS) — no central registry to edit. This means plugins can define their ownSignalsubclasses (for their ownThreads) without ever touching this file.
-
class BasicSignal : public Limef::signal::Signal¶
- #include <signal.h>
A thread intercom Signal.
A signal that is used by a
Threadfrontend to intercom with theThreadbackendPublic Types
-
class FlowControlSignal : public Limef::signal::Signal¶
- #include <signal.h>
Flow control signal for framefilter chains.
Used to send control commands (like flush) through framefilter chains. Producer threads send this signal downstream when stopping.
-
class NullSignal : public Limef::signal::Signal¶
- #include <signal.h>
A dummy/placeholder signal class & a minimal example of creating a new signal class.
-
class Signal¶
- #include <signal.h>
Signal base class.
Signals are encapsulated into
SignalFrames and they are used to informThread’s and downstream framefilters about actions and parameters they should do and use.Use the
SIGNAL_CLASS(ClassName)macro in every concrete subclass to implementgetSignalClass(),clone(), andstaticSignalClass()(used bySignal::as), for example:class MySignal : public Signal { SIGNAL_CLASS(MySignal) public: ... };
Subclassed by Limef::rtsp::RTSPServerSignal, Limef::signal::BasicSignal, Limef::signal::FlowControlSignal, Limef::signal::NullSignal, Limef::thread::ExampleSignal, Limef::thread::MediaFileSignal, Limef::thread::USBCameraSignal, Limef::thread::WebSocketServerSignal, Limef::webrtc::WebRTCServerSignal
-
using SignalClass = std::type_index¶