Request for clarification of inner working of Addressable cache and download behaviours

Hiya,

It would be awfully nice to have more control over the Addressable download/caching/loading. Right now it feels like a magic box. Here are a few things I'm running into that I would like to be able to properly handle. All those use cases are a variation on:

• there is a new version of the remote bundle available (dnloadSize>0)
• there may be a previous version of the same bundle in the cache
• I might want to load from the cache instead of downloading

Here we go:

• can I load from cache instead of downloading (in the case a new version of the remote bundle is available)?
• what happens if a download fails due to poor connection but there is a previous version of the bundle in the cache?
• can I tell if a bundle is in the cache when it shows a dnloadSize>0
• how long does a bundle stay in the cache?
• under which condition does a bundle gets removed from the cache?

With my current understanding of Addressables, that data/functionality doesn't exist. Yet I feel they are necessary before Addressables can be used in complex released product. Am I missing something?