Open Zsailer opened 2 years ago
Another idea sparked by https://github.com/jupyter/jupyter_client/issues/838.
Today, both the control and shell channel can trigger IOPub status messages, but there is no easy way to tell which parent channel caused a given IOPub message. We could add "channel" as part of the IOPub's message specification, e.g.:
{ ... "parent_header": { "channel": "shell", ... }, "execution_state": ... }
I like this solution. It should probably go in the content of the status message, since it's specifying what is idle/busy/etc.
content
Another idea sparked by https://github.com/jupyter/jupyter_client/issues/838.
Today, both the control and shell channel can trigger IOPub status messages, but there is no easy way to tell which parent channel caused a given IOPub message. We could add "channel" as part of the IOPub's message specification, e.g.: