The channel a notification named.
The channel's name.
The channel.
Whether a channel is registered under this name.
The names of every registered channel.
Register a built channel.
The channel.
This manager.
Register a channel to be built on first use.
The name notifications refer to it by.
How to build it.
This manager.
StaticcreateA manager.
StaticgetThe published manager, if there is one.
StaticsetPublish the manager, so code outside the container can reach it.
Optionalmanager: NotificationManager
Holds the configured channels and hands one out by name.
The same shape every driver-based module in the framework uses, and the same lifetime: built for one event, like the container it belongs to. It is a registry of factories, so rebuilding it costs nothing. Nothing here holds state between events; a channel that needs a connection holds it itself, because a connection is a resource and the channel is the boundary that owns it.