> > > Why aren't you caching the data yourself, so you can control the location, > size, and retention policies of the cache? Conversely, why are you > electing to have those functions -- which are essential to the operation > of your product -- be delegated to a component (WebView's cache) over > which you have no real control? >
Now that I have implemented a new caching mechanism for ReaderScope that is independent of WebView, the added control looks like a big advantage. Thanks for the advice. Jayesh --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
