Perhaps create an (abstract) interface / abstract class TileProvider? Not sure, if there is an use case.
Perhaps separation between http download and tile providing since http download is needed for wikipedia (and perhaps other stuff) integration also.
What about redirects? in general it seems to be a good idea to support them, but do we also need the ability to forbid redirects of inform the user?
The TileLoader should be able to handle not only files, but also QByteArrays or whatever is delivered by the network plugin interface.
Here are drop notes of understanding how downloading http stuff happens:
HttpDownloadManager is the entry point if you want to download http things.
A StoragePolicy belongs to the HttpDownloadManager to handle downloaded files properly.
In the current imlementation (trunk just after 4.4 branching), there are many HttpDownloadManagers, which in turn have their own PluginManager, StoragePolicy and DownloadQueueSets. This looks suboptimal and hard to evolve.
- Work is ongoing to have only one PluginManager belonging in the MarbleModel, which others could use when needed, currently
So HttpDownloadManagers would need to use it.
- Many HttpDownloadManagers created "in the wild" for different purposes, like in
* AbstractDataPluginModel (and so all *PluginModel which inherit...), * MarbleModel, * TwitterPlugin
Maybe one would be enough, given the DownloadQueues and StoragePolicies framework...
to be done