Creates a new instance of the driver.
Indicates whether the driver is currently active. Subclasses must keep it
in sync with their connection: signaling messages are only published while
the driver is active, and joined rooms announce themselves again when it
becomes active. A namespace that fails on its own leaves the driver
active, and emitting active once it is subscribed again makes rooms
announce themselves to the peers they missed.
Sets the active state of the driver and emits corresponding events.
Destroys the driver instance, cleaning up any resources.
Emits inactive if the driver was active, then removes all event handlers.
Emits an internal event with optional data.
The event name.
The data to pass to event handlers.
Unregisters an event handler for the specified internal event.
The event name.
The event handler function to remove.
Registers an event handler for the specified internal event.
The event name.
The event handler function.
Optionaloptions: { signal?: AbortSignal }
Listener options.
Optionalsignal?: AbortSignalRemoves the handler when aborted.
A function that removes the handler.
Publishes a signaling message to the specified namespace.
The namespace to publish the message to.
The message data to publish.
Nothing directly; resolves once the message is delivered (async drivers may return a promise).
Subscribes to signaling messages for the specified namespace.
The namespace to subscribe to.
The handler function to call when a message is received.
Nothing directly; resolves once the subscription is established (async drivers may return a promise).
Unsubscribes from signaling messages for the specified namespace.
The namespace to unsubscribe from.
The handler function to remove.
Nothing directly; resolves once the unsubscription is confirmed (async drivers may return a promise).
In-memory signaling driver for intra-process communication.
This driver is useful for testing and debugging purposes, but is not suitable for production use due to its limitations (e.g., a single-process scope).
Example