Closed febg11 closed 3 years ago
Because you did implement you indeed have to implement concurrentFetches, if you do extend you would get the default of 5. The web helper now has a queueing mechanism. Because some servers are not happy when you request many files at the same time you can indicate how many requests you can have simultaneously (the concurrentFetches) and the rest will be queued.
JsonCacheInfoRepository is a way to store information about your cache. The default on mobile and mac was (and is) that it is stored in an sqflite database. However, because on windows and linux sqflite is/was not supported and is actually quite some overhead we added JsonCacheInfoRepository. This stores the data in a simple file as a json string and parses it on load. So perhaps in some time the default on all platforms will be JsonCacheInfoRepository, but for that we have to make migrations.
The setup of your config is fine.
Hi
I have just updated cache manager to 2.1.1 (was on 1.4.2) and I just want to check there are no other behaviour changes, as you wrote 'expects a Config object with some settings you were used to, but some are slightly different'.
I have created a short cache manager which should only store files for 1 day 3 hours with a max cache amount of 300. My setup for this is below.
I think the Config() part is ok but wanted to double check the FileService doesn’t need to be changed. I only got an error asking to implement the concurrent fetches, is everything else alright to leave the same?
Thanks a lot
... Edit
Also could you explain what JsonCacheInfoRepository does?