Hi @Shachar Itzhaky , turns out that Put / Get are only used by jsoo
So if we have jsoo use the server-side package manager
they get unused.
I'm unsure if we should get rid of them (for now); it is clear that we need a server-side FS API for the git backend, but my impression is that we may need to think about it from scracth, WDTY?
In particular I think stuff like the git js mode
assume their own fs implementation
yeah well I was also using Get
/Put
for compiling in the browser
but perhaps that's not the right way either
Well for sure we need an API to manage the FS of the worker
I guess the main question is if the API will have to transfer files from client / server
or will just request the server to download/upload urls
at least compiled .vo files have to be sent from the server to the client. But perhaps we can send all of the compiled files in one bundle instead of having the Get each one; same for passing the sources from the client to the server.
for pkgs yeah it seems that only the url needs to be passed
When do the .vo files go back to the client?
the previous way I did it was a mess: the server would send a ["Compiled", "out.vo"]
to the client, then the client would ["Get", "out.vo"]
.
why does the client need the .vo file?
good point actually; for checking documents that use the .vo the files might as well just stay in the server; tho I found that it is better to launch a separate Worker for batch compilation, so at least the files need to transfer between the "compile" worker and the "interactive" worker.
that's a very good point
Would be nice if the FS would be actually be a sharedmemory worker or something like that
funny you should mention that, I actually implemented one for WASM. but it's not very stable and kinda slow.
This kind of stuff makes sense IMHO as for example once we get the core stable
I'd much like to have a worker that is contionously fed by the main worker
and whose job is to run search all the time to present suggestions to the user :D
Last updated: May 31 2023 at 03:30 UTC