Architecture of Plugin

[ciyer]

Description

The current architecture of the extension is not viable. The correct way to structure the extension is as a combination of client extension and server extension.

One model could be the Dask lab extension which uses the jupyter-server-proxy to manage the service.

References

• server-extension "hello world"
• https://github.com/dask/dask-labextension
• https://jupyter-server-proxy.readthedocs.io/en/latest/index.html

[rokroskar]

For the backend, I suppose the only thing needed is to implement the load_jupyter_server_extension function that would start the flask core-service app.

[rokroskar]

Actually, we need to verify that a tornado app is not a requirement. From their docs it sounds like it is, but I don't see why it would need to be since it just needs to provide an API.

It seems there are three concepts here:

• a JupyterLab extension
• a jupyter server extension
• a jupyter server proxy

I think the difference between a jupyter server proxy and a jupyter server extension is that the latter may need to implement tornado handlers. Perhaps we can use a server proxy together with a jupyterlab extension though.