We currently communicate from TypeScript <-> Python using a sidecar process. We start a new process whenever we need to communicate. data is sent to Python as a JSON command-line argument and we read JSON back from stdout.
With the web version of RefStudio (#347) we have an HTTP server. This means that the web version and the desktop version have two different ways of communicating. Ideally we'd make the desktop app use the HTTP server as well so that we can unify these code paths.
See @hammer's comment here for some context: #17 (comment)
The simplest path forward is to use Command to spawn the web server and then Tauri's version of fetch to communicate with it.
We currently communicate from TypeScript <-> Python using a sidecar process. We start a new process whenever we need to communicate. data is sent to Python as a JSON command-line argument and we read JSON back from stdout.
With the web version of RefStudio (#347) we have an HTTP server. This means that the web version and the desktop version have two different ways of communicating. Ideally we'd make the desktop app use the HTTP server as well so that we can unify these code paths.
See @hammer's comment here for some context: #17 (comment)
The simplest path forward is to use
Commandto spawn the web server and then Tauri's version of fetch to communicate with it.