Skip to content

Latest commit

 

History

History
58 lines (32 loc) · 3.47 KB

File metadata and controls

58 lines (32 loc) · 3.47 KB
graph LR
    Signal_Registry["Signal Registry"]
    NamedSignal["NamedSignal"]
    Sender["Sender"]
    Receiver_Subscriber["Receiver/Subscriber"]
    Signal_Registry -- "creates/retrieves" --> NamedSignal
    Sender -- "accesses" --> Signal_Registry
    Sender -- "dispatches via" --> NamedSignal
    Receiver_Subscriber -- "connects to" --> NamedSignal
    click Signal_Registry href "https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/blinker/Signal_Registry.md" "Details"
Loading

CodeBoardingDemoContact

Details

The Blinker subsystem provides a robust in-process signaling mechanism, primarily centered around the NamedSignal component. The Signal Registry acts as a central factory, ensuring unique NamedSignal instances are available for specific event channels. Sender components initiate events by dispatching signals through the NamedSignal's send method, while Receiver/Subscriber components register their interest with NamedSignal via its connect method to execute predefined logic upon signal dispatch. This architecture facilitates a decoupled, event-driven communication flow within an application, where components can interact without direct dependencies, enhancing modularity and flexibility.

Signal Registry [Expand]

A global factory and registry responsible for creating and retrieving Signal instances, particularly named ones. It ensures that for a given name, a unique Signal object is always returned, facilitating signal discovery and reuse across an application.

Related Classes/Methods:

NamedSignal

Represents a specific named event channel. It directly manages the list of connected receivers and the dispatching logic for that particular signal. It is the concrete "subject" in the Observer pattern.

Related Classes/Methods:

Sender

Components that initiate events by dispatching signals. They act as the "publishers" or "observables" in the event system, interacting with NamedSignal instances by invoking their send method.

Related Classes/Methods:

Receiver/Subscriber

Components that register interest in specific signals and execute predefined logic when those signals are dispatched. They act as the "observers" in the event system, connecting to NamedSignal instances by registering themselves via the connect method.

Related Classes/Methods: