Simplify interface and make lib truly asynchronous about disklrucache HOT 4 CLOSED

Synchronous pushes threading model to the caller who's often on a BG thread already (e.g., making an HTTP call). Complex entries are needed as your parameterized API offers no explanation of how complex key value types are serialized. And finally, this is not an Android library so it cannot know about getCacheDir().

Either write a high-level wrapper or use another library. These changes will not be made.

from disklrucache.

Ok, getCacheDir() is not needed.

But complex entries is not needed - just allow caller to supply serializer to/from byte[].

This is not android library, but most usages for such cache is on the android, because servers use Redis/Memcache and other distributed services for caching and your solution is not scalable.

from disklrucache.

I shipped something similar in a different library and it was a terrible
decision for something at this level. I will not be adding it here so you
are welcome to try your ideas in a fork or a separate library.

On Sat, May 2, 2015, 2:22 PM Virl [email protected] wrote:

Ok, getCacheDir() is not needed.

But complex entries is not needed - just allow caller to supply serializer
to/from byte[].

This is not android library, but most usages for such cache is on the
android, because servers use Redis/Memcache and other distributed services
for caching and your solution is not scalable.

—
Reply to this email directly or view it on GitHub
#80 (comment)
.

from disklrucache.

Thanks, I'm already thinking about making my small library for android disk cache. Maybe if it will be finished, I will post it to github.

Btw, look at your forks: most of them are fixes for Android. There is even separate wrapper library called Reservoir (but unusable due to poor design).

from disklrucache.