Doug, Greg...
I've calmed quite a bit ;)
As a (new android market) developer, I was making updates and
expecting that the latest would always be the one coming down for me
to verify. Now that I've 'institutionalized' my release process with
scripts, etc. *and* understand what the heck was going
I've noticed that the Market app client has its own cache that it will
consult. If you force the Market app to terminate, you're more likely
to see fresh results from the server.
Doug
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post
For those thinking I meant a BROWSER's cache -- perhaps I was not
clear... I meant that on the PHONE,the MARKET APPLICATION has a
cache. (Settings = Applications = Manage Applications = Menu: Show
ALL = Choose MARKET. You'll see a button to CLEAR CACHE.
And my point is -- why would the
On 4 October 2010 14:32, tony obrien tobsourcecode...@gmail.com 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.
On Mon, Oct 4, 2010 at 7:32 AM, tony obrien tobsourcecode...@gmail.comwrote:
And my point is -- why would the designers of that APP use a cache?
Images, descriptions, comments, app lists you just viewed?
Try this: after you clear the market cache, open it up and navigate to some
app. See how
Hi Tony!
I experienced the same thing last Friday! I updated my app but when I
checked the market it still shows the old version. I was in a panic
too! ;)
I forced the Market app to terminate and then restarted it (pretty
much what Doug said, eh?), and it showed the update. I am not sure if
Keep in mind that phone apps are/should be designed to minimize
network traffic. So caching is a good thing, generally. The Market
app is designed to sell stuff, not give the developers warm fuzzies.
On Oct 4, 3:33 am, Zarah Dominguez zarah.doming...@gmail.com wrote:
Hi Tony!
I experienced
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 }
On Oct 4, 11:46 am, tony obrien tobsourcecode...@gmail.com wrote:
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
On Mon, Oct 4, 2010 at 3:05 PM, Doug beafd...@gmail.com wrote:
Take a breath, get a cup of coffee (or cut down on the coffee!).
Everything's going to be all right. Your situation is the exception,
not the rule. :-)
The simplest solution is to not open the Market app before you're
about to
Are you talking about a cache on the server side, or a cache in your
browser? There's no way for the server side to (reliably) control
what your browser caches. If you suspect it needs to be refreshed you
can press Refresh on most browsers and that will refresh the page
(though I don't offhand
Given the global scale of the Marketplace, some update latency is to
be expected. There is, no doubt, a central master database of
applications but you can bet that the database is replicated out to
dozens of local copies around the globe. This replication process is
usually completely decoupled
12 matches
Mail list logo
