Event that fires when a process disconnects from the network, carrying the names of the methods
its departure removed from the central registry.
This is platform-internal core plumbing between the process that owns the websocket server and
the services that know how their own registered names are formed, not part of the @papi/*
surface.
A process that goes away abruptly — most commonly a window the user closed — announces nothing on
its way out, so this is derived from the connection teardown itself: it is emitted only once the
departed process's methods are out of the registry, and therefore cannot report a death that has
not finished happening. Only the process holding the websocket server can observe a connection
being lost, so this only ever fires there; elsewhere it is a real event that never fires, which
lets shared code subscribe without knowing which process it is running in.
Event that fires when a process disconnects from the network, carrying the names of the methods its departure removed from the central registry.
This is platform-internal core plumbing between the process that owns the websocket server and the services that know how their own registered names are formed, not part of the
@papi/*surface.A process that goes away abruptly — most commonly a window the user closed — announces nothing on its way out, so this is derived from the connection teardown itself: it is emitted only once the departed process's methods are out of the registry, and therefore cannot report a death that has not finished happening. Only the process holding the websocket server can observe a connection being lost, so this only ever fires there; elsewhere it is a real event that never fires, which lets shared code subscribe without knowing which process it is running in.