An asynchronous, persistent key-value store created for writing desktop and mobile applications, based on SQLite3. Akavache is great for both storing important data as well as cached local data that expires.
Do you want to request a feature or report a bug?
features
What is the current behavior?
Currently if the resilient SqlLite storage blobs don't get registered for whatever reason (missing package or linked out) then everything just runs as normal against InMemory cache which isn't obvious to the user
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Use Akavache on iOS without Preserving the SQLiteEncryptedBlobCache and it'll just run against InMemory whereas Android will run against Sql Lite
What is the expected behavior?
I'm thinking a warning message just to the debug output saying something like
Warning: Currently this is just using InMemory cache if you are wanting to use the resilient SqlLite cache check that "SQLiteEncryptedBlobCache" isn't being linked out.
This can just be included with the InMemoryBlobCaches that get registered in Registration.cs so warning just outputs first time
What is the motivation / use case for changing the behavior?
Limit Confussion
Decent idea; maybe careful about language of "SQLiteEncryptedBlobCache" what happens if a consumer (non-technical) person comes across this message in their logs?
Do you want to request a feature or report a bug? features
What is the current behavior? Currently if the resilient SqlLite storage blobs don't get registered for whatever reason (missing package or linked out) then everything just runs as normal against InMemory cache which isn't obvious to the user
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Use Akavache on iOS without Preserving the SQLiteEncryptedBlobCache and it'll just run against InMemory whereas Android will run against Sql Lite
What is the expected behavior? I'm thinking a warning message just to the debug output saying something like
This can just be included with the InMemoryBlobCaches that get registered in Registration.cs so warning just outputs first time
What is the motivation / use case for changing the behavior? Limit Confussion