Name of the network event main emits when the app quits. No payload. On an explicit quit (Cmd+Q,
the Quit menu item, platform.quit or platform.restart) it is emitted before any window is
destroyed, and a window uses it to read the death of its own connection a moment later as the app
going away rather than as a failure.
When closing windows shuts the app down instead (a close-all from the primary window's close
button, or closing the last window on Windows and Linux), it is emitted only after every window
is gone, so no window sees it. Those windows need no hint: each one's connection was closed
cleanly, as a normal close rather than a failure, before the window was destroyed. Other peers,
such as the extension host, still receive it. Best effort even on an explicit quit: delivery is
asynchronous and a window may be gone before it arrives, so a subscriber must still cope without
it.
Name of the network event main emits when the app quits. No payload. On an explicit quit (Cmd+Q, the Quit menu item,
platform.quitorplatform.restart) it is emitted before any window is destroyed, and a window uses it to read the death of its own connection a moment later as the app going away rather than as a failure.When closing windows shuts the app down instead (a close-all from the primary window's close button, or closing the last window on Windows and Linux), it is emitted only after every window is gone, so no window sees it. Those windows need no hint: each one's connection was closed cleanly, as a normal close rather than a failure, before the window was destroyed. Other peers, such as the extension host, still receive it. Best effort even on an explicit quit: delivery is asynchronous and a window may be gone before it arrives, so a subscriber must still cope without it.