Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document kernel message additions by Jupyter server #869

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jasongrout
Copy link
Contributor

We also document things about kernel message buffering, rate limiting, etc.

This migrates jupyter/notebook#3765 to the Jupyter Server repo, where the kernel message additions now happen.

Setting as draft since there are some TODOs to take care of.

jasongrout and others added 2 commits June 14, 2022 13:08
We also document things about kernel message buffering, rate limiting, etc.

This migrates jupyter/notebook#3765 to the Jupyter Server repo, where the kernel message additions now happen.

TODO

Document the session URL parameter used in kernel connections. Is that
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From @minrk at jupyter/notebook#3765 (comment)

Yes, we should document it. sessions_id is associated with each specific client. It's entirely unrelated to the session rest API. The session_id here is the message protocol header.session field, which is used on replies and iopub to identify the original sender of the message. The main important use of this session_id is setting zmq.IDENTITY on reconnects to ensure that replies intended for this client still arrive there after reconnects. It's also used to build messages created in the notebook server for this client, but I'm not sure we should commit to or rely on that yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant