> 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.
You're very welcome. Best of luck, um, scoping your readers, or whatever. ;-)
--
Mark Murphy (a Commons Guy)
http://co
>
>
> 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
>
On Wed, Sep 23, 2009 at 7:53 PM, Mark Murphy wrote:
>
> >> 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 u
>> 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
On Wed, Sep 23, 2009 at 7:00 PM, Mark Murphy wrote:
>
> > But given
> > the large amount of webview cache that my app tends to accumulate over
> > time,
> > I need to relocate this cache on SDCard.
>
> Why not just call clearCache() periodically?
>
No, I don't want to loose the cache. In fact, Re
> But given
> the large amount of webview cache that my app tends to accumulate over
> time,
> I need to relocate this cache on SDCard.
Why not just call clearCache() periodically?
--
Mark Murphy (a Commons Guy)
http://commonsware.com
Android App Developer Books: http://commonsware.com/books.ht
6 matches
Mail list logo
