-
Notifications
You must be signed in to change notification settings - Fork 273
Memory cache #22
Comments
read it yesterday, too. After checking the implementation I'm not sure if it is possible with Tray because Remember doesn't work multiprocess, it's only thread safe. Side note: Having Guava as a hard dependency for a single class SharedPreferences wrapper seems wrong. I'm currently working on dataChangedListeners which work multiprocess. Once they are complete I'm confident an in memory layer which updates itself based on the listeners is possible. |
Hey Pascal, I agree that guava as a dependency for an android app is a nightmare. But I am not sure to understand why you couldn't build a memory cache |
It's only the multiprocess thing. If you have two processes, a SyncAdapter and your Application UI, there will be two instances of the memory cache. Although the memory cache is a singleton! So they are working on two different data sets and both instances wont know about each others changes. |
Humm, I must get more familiar with Tray before going on this thread. I am Thx for your answers, 2015-05-18 8:33 GMT-07:00 Pascal Welsch notifications@github.com:
|
A memory chace is now possible with new data changed listener which can be used to sync the database with the cache in the background |
Listener work as expected. I'll focus on the memory cache now |
Would it be possible to add a memory cache mechanism to Tray to boost its performances.
Something inspired by https://github.com/tumblr/Remember ?
The text was updated successfully, but these errors were encountered: