Comment 1 for bug 1574766

Having looked a bit further into this, it seems the only case we're likely to run into problems is where an embedded package is removed from the store entirely during the client cache validity period. In this case, the client will present its cached view, and once the user selects the removed package in the highlight, the client will request the details page and the index will return a 404. Once the cache expires and the device re-requests the top-level resource, the response will be recomputed and will not include the removed package.

In light of this, we will reconfigure the default cache expiry to be 3,600 seconds (1 hour) and suggest that the click scope be slightly smarter, invalidating its local cache when encountering 404 responses for embedded resources.