OptionalcommsWhether comm messages should be sent to kernel subshells, if the kernel supports it.
Sending comm messages over subshells allows processing comms whilst processing execute-request on the "main shell". This prevents blocking comm processing. Options are:
A signal emitted when there is a server API connection failure.
ReadonlydisposedA signal emitted when the object is disposed.
ReadonlyisWhether the manager is active.
ReadonlyisReadonlyisWhether the manager is ready.
ReadonlyreadyA promise that resolves when the manager is initially ready.
A signal emitted when the running kernels change.
ReadonlyrunningThe number of running kernels.
ReadonlyserverThe server settings for the manager.
Connect to an existing kernel.
A promise that resolves with the new kernel instance.
Dispose of the resources held by the object.
If the object's dispose method is called more than once, all
calls made after the first will be a no-op.
It is undefined behavior to use any functionality of the object after it has been disposed unless otherwise explicitly noted.
Start a new kernel.
A promise that resolves with the kernel connection.
The manager serverSettings will be always be used.
Object which manages kernel instances for a given base url.
Notes
The manager is responsible for maintaining the state of running kernels through polling the server. Use a manager if you want to be notified of changes to kernels.