You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all queries go through a fresh interpreter. It would be nice to keep them alive so they can keep their knowledge base contents between requests.
I'm not sure how easy it will be because the stdin interfaces for Go WASM libraries don't look so great. Would be really nice to be able to pass an io.Reader to them.
Might be possible to work around by exporting Go/C functions and calling from Trealla FFI (need to add FFI to Trealla WASM first).
The text was updated successfully, but these errors were encountered:
One crazy trick I tried was using mkfifo and reading from inside WASM and it seems to work fine, so I'm thinking we can use FIFOs as a kind of temporary workaround. This won't work on Windows but neither does wasmer-go at the moment.
Played around with named pipes. I think it could probably work but it adds a lot of complexity, including filesystem stuff that I would rather avoid. At that point it's probably better to just execute tpl in a subprocess.
I think exposing a host function is the best option, probably. Not sure how to actually do this yet.
Currently all queries go through a fresh interpreter. It would be nice to keep them alive so they can keep their knowledge base contents between requests.
I'm not sure how easy it will be because the stdin interfaces for Go WASM libraries don't look so great. Would be really nice to be able to pass an
io.Reader
to them.Might be possible to work around by exporting Go/C functions and calling from Trealla FFI (need to add FFI to Trealla WASM first).
The text was updated successfully, but these errors were encountered: