OK, I'll concede that the cache is useful for the WEB (or web-like)
aspects of the MARKET app -- but (it still) seems to me that if its
MAIN FUNCTION is to provide d/l of apps, then those app 'references'
should not be cached but should always be refreshed.
On Oct 4, 9:30 am, "{ Devdroid }" <[email protected]> wrote:
> On 4 October 2010 14:32, tony obrien <[email protected]> wrote:
>
> > And my point is -- why would the designers of that APP use a cache?
> > It doesn't 'minimize network traffic' since it always seems to go up
> > to the net anyway to do a D/L....
>
> Cache in Market app does reduce network traffic.
>
> > And having to either KILL the MARKET app on the device, or Clear its'
> > cache still confounds me as to why it has one at all.
> > If the thing is smart enough to know when an update is ready, why
> > isn't it smart enough to know that its' cache is stale?
>
> You do not have to do that. Sparringly Market may lag a bit
> when you update anything, but it does not last too long.
--
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
