Hi Developers Of Android, I am trying to figure out a way to implement a in-memory cache; but its size will be relatively big by comparison with the dvm heap size. I had planned to use nio and/or Parcel class to serialize my objects then store them on the native memory; however i cannot predict the performance of reconstructing those objects from their bytes indeed. Furthermore, i couldn't have found anything useful which teaches how to use Parcel and Parcelable to do some custom serialization. I know it is for IPC in android; and i didn't find inspecting the Parcel.cpp to understand the internals of the Binder protocol so fascinating and feasible. On the other hand, I cannot make use of LRUCache class either due to the dvm heap size limit which means that i will not be able to store my java objects on the dvm heap as they are. According to the researches on the web i've made so far, the only way to exceed the dvm heap size is to tell my clients to root their devices before they install my application(or i misunderstood. If that is the case, please do correct me.) so they can modify the heap size option of their devices.
I am trying to avoid NDK to implement the cache for now, since i have to pass my c/c++ instances to the java side eventually. Long story short, Would any developer mind telling me the best way to implement an in-memory cache which may penetrate dvm heap size limit and run fast as well? Or At least, if you can send me some links, pdfs, ebooks, docs, etc for me to check them out; that woul be really great! Thanks, Ilker GURCAN -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
