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

Add kernel and session architecture diagram #7809

Closed
jtpio opened this issue Jan 22, 2020 · 3 comments · Fixed by #8015
Closed

Add kernel and session architecture diagram #7809

jtpio opened this issue Jan 22, 2020 · 3 comments · Fixed by #8015
Labels
documentation pkg:services status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.

Comments

@jtpio
Copy link
Member

jtpio commented Jan 22, 2020

There is currently a good overview of the different kernel related concepts in the services README.md

I wonder whether there could also be a diagram that explains how all the different components talk to each other. Maybe something similar to the one posted in #7252 (comment):

image

Maybe the exact same diagram could be used, unless some of the inner details have changed.

@vidartf
Copy link
Member

vidartf commented Jan 29, 2020

I think this is still accurate in explaining how things are in the most common case in lab, but @jasongrout would have to confirm.

@jasongrout
Copy link
Contributor

The "ClientSession" is now "SessionContext", but other than that, I think it is still essentially accurate. I suppose it's a little confusing that SessionConnection contains KernelConnection, but SessionContext is off to the side. In reality, SessionContext has a reference to a SessionConnection (or null), which in turn has a reference to a KernelConnection (or null). Thanks!

@jasongrout
Copy link
Contributor

And I suppose all the "WS Bridge" boxes should be inside a "Jupyter Server" box to indicate that they are part of the server.

@lock lock bot added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Apr 15, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation pkg:services status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants