>> Why not just call clearCache() periodically? >> > > No, I don't want to loose the cache. In fact, ReaderScope is a Google > Reader > client that caches the news web pages in the background using webview. > This > allows the user to access these webpages offline later on.
And what happens when you fill up their SD card with your cache? 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, ideally, you could create your own CacheManager and WebViewDatabase refinements, so you could leverage 90% of the existing logic and only change what is needed to fit your business needs. Alas, I see no evidence that you can replace the CacheManager/WebViewDatabase used by a WebView. -- Mark Murphy (a Commons Guy) http://commonsware.com Android App Developer Books: http://commonsware.com/books.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
