Quoth Drake Wilson , on 2013-06-07 08:18:05 -0500:
> Actually, I dropped a paragraph on the floor, sorry. It's probably better to
> use
> xRead for this, since in that case SQLite will manage its own memory for the
> cache
> of decrypted pages. The loss in that case, if you still use mmap behin
Quoth Drake Wilson , on 2013-06-07 08:14:27 -0500:
> If you really want, you might be able to implement xFetch to allocate a shadow
> buffer, decrypt from the map into that, and return that pointer. Since it's
> designed for accessing maps directly, though, I don't see it documented what
> the lif
Quoth Paul Vercellotti , on 2013-06-07 01:07:35 -0700:
> The current system does in-place decryption on read (no copying), which adds
> almost no overhead to the operation. Now in-place decryption with a
> memory-mapped file seems like it would dirty the page, which could
> accidentally get flus
Hi there,
We use a vfs-based obfuscation system using the old xRead and xWrite methods.
I'm wondering if these can be adapted to work with the new memory-mapped i/o
functionality in a way that still has the advantages of memory-mapped i/o?
The current system does in-place decryption on read
4 matches
Mail list logo
