Add Jupyter Comms as a supported backend

Kitware / wslink

Python/JavaScript library for communicating over WebSocket

https://kitware.github.io/wslink/

BSD 3-Clause "New" or "Revised" License

83 stars 26 forks source link

Add Jupyter Comms as a supported backend #129

Closed banesullivan closed 7 months ago

banesullivan commented 1 year ago

aiohttp is the only currently supported backend for wslink. Could we use the Jupyter comms implementation as a "backend" for at least the client-server communication?

This would prevent the need for using jupyter-server-proxy with wslink and trame to view Trame-based UIs in Jupyter.

Reference: https://jupyter-notebook.readthedocs.io/en/stable/comms.html

banesullivan commented 1 year ago

Maybe AnyWidget could be a more viable and robust route: https://anywidget.dev/blog/introducing-anywidget/

jourdain commented 1 year ago

This is even further apart from what wslink offers...

banesullivan commented 1 year ago

Well shucks...

jourdain commented 1 year ago

You think UI instead of network.

banesullivan commented 1 year ago

Yes -- still wrapping my head around anywidget (just stumbled upon this in the last 10 minutes). But I think there may be a way to leverage it to work around the Jupyter issues we face with jupyter-server-proxy. I'll investigate and try to report back when I have the time

jourdain commented 7 months ago

done