Document a high level technical overview on how this project work about jupyter-remote-desktop-proxy HOT 3 OPEN

websockify also intercepts the VNCserver's TCP socket bind request (e.g. to 5901), transparently changes the internal library call so that the VNCserver binds to <random-port>, and websockify listens on the original specified port (5901) instead. See the Wrap a Program section of https://pypi.org/project/websockify/#description

from jupyter-remote-desktop-proxy.

Ah, but we can't make use of that right? We need to specify it so that jsp proxies to what websockify exposes right? I errored without #99 in turbovnc listening to a random TCP port

from jupyter-remote-desktop-proxy.

Hi @consideRatio,
I am seeking clarification regarding the usage and capabilities of the Jupyter Remote Desktop Proxy, as I found the README lacking in providing an overview of its use cases and functionalities.
Our current setup involves a JupyterHub server and five Jupyter Notebook servers. The JupyterHub server serves as a proxy, directing users to their respective Jupyter Notebook servers based on their user group.
Now, we have a specific requirement: we want users to access every notebook session through a VNC session to ensure the security of our files and prevent unauthorized downloading and copying of contents.

Here are the questions I need clarification on:

1. Can we utilize the Jupyter Remote Desktop Proxy to proxy our JupyterHub in a way that enables opening a notebook session within a VNC desktop session?
2. If such proxying is possible, I'd like to understand whether the VNC sessions opened will be dynamic or static. For instance, if user A logs into the JupyterHub and user B also logs in, will they each receive separate VNC desktop sessions? It's crucial that each user has their own isolated desktop session, ensuring changes made in one user's Jupyter Notebook do not reflect in another user's desktop session.

from jupyter-remote-desktop-proxy.