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
I have a use-case where I'd like to serve a table created in duckdb-wasm.
I wanted to experiment doing this with this extension, however I'm getting an error when trying to load it:
Should it even work on the wasm version?
The text was updated successfully, but these errors were encountered:
Hello @raziele the http_server extension does not support WASM as it cannot expose sockets and services. We're working on a websocket based option to allow these interactions, but its still an early prototype. Unfortunately at this time you can only connect from WASM to DuckDB http_server(s) but not the other way around if not by using the client itself as "middleware" between the two connections. If there's interest we can turn this into a feature request and push this up the roadmap.
Hey @lmangani thanks for the quick reply!
No rush. Let me just describe the use-case to enrich future discussions:
For context, I'm building a data tool that helps users process sensitive data. Using duckdb-wasm, I can build the tool to run entirely on client side so 100% privacy.
One of the requested features is to do custom analysis on the data, so my thought was to let users temporarily serve the data and allow them to fetch it in their preferred analysis tool. For example - using Google Sheet IMPORTDATA function.
I have a use-case where I'd like to serve a table created in duckdb-wasm.
I wanted to experiment doing this with this extension, however I'm getting an error when trying to load it:
Should it even work on the wasm version?
The text was updated successfully, but these errors were encountered: