3 ms·
I really like the idea of using FUSE as SQLite backend, rather than injecting into the process I love the use case of querying SQLite from a CDN with range req
by conradev 4y ago
I really like the idea of using FUSE as SQLite backend, rather than injecting into the process
I love the use case of querying SQLite from a CDN with range requests, because it allows for real “serverless” querying. For example, this: https://github.com/psanford/sqlite3vfshttp https://github.com/psanford/sqlite3vfshttp
- losfair 4y ago> I love the use case of querying SQLite from a CDN with range requests Author here. Actually I have a similar idea with mvSQLite. Provide a client-side-queryable API, but read-write instead of read-only. Security can be implemented with a "provenance"-style mechanism: the client proves they reached a page following a valid/allowed path, by presenting the path (along with necessary signatures) to the server. That way we can have "serverless" read-write transactions with table-level security.
- conradev 4y agoInteresting! I had not thought about access controls when all of the pages are mixed together, but that makes sense. Have you thought about encryption? Is it possible to do client-side symmetric encryption?