The fast and very technical answer is that you get search results on encrypted data by making liberal use of the cheap containers to automatically save indexes as the data is modified. But note how our timeline includes the Object Database having advanced features (save triggers, derived objects like indexes) that do this for you. (Full text search and similar features.)
Note also that we built this in about 3 weeks so it's minimal, but will grow fast. See the timeline section on the site.
For code examples, look in the GitHub checkout under client/examples. For understanding the server's data structures, look at server/lib/stores/postgresql/setup.sql.
I'd like to see some way to combine public-key crypto (receiving and encrypting incoming unencrypted mail, received over starttls) with periodic mail indexes built on the client, so you could search a server-hosted encrypted mailbox.
> search results on encrypted data by making liberal use of the cheap containers to automatically save indexes as the data is modified.
That's nice to read: I ended up with that for an application I'm responsible for. I was pleased with what I came up with, but it's one of those things where end users think something like "oh, huh, nice, you can finally do search on this site", but they don't have any idea how difficult it is!
The fast and very technical answer is that you get search results on encrypted data by making liberal use of the cheap containers to automatically save indexes as the data is modified. But note how our timeline includes the Object Database having advanced features (save triggers, derived objects like indexes) that do this for you. (Full text search and similar features.)
Note also that we built this in about 3 weeks so it's minimal, but will grow fast. See the timeline section on the site.
For code examples, look in the GitHub checkout under client/examples. For understanding the server's data structures, look at server/lib/stores/postgresql/setup.sql.
Thanks for your interest!