core (memory/cache): file caching handling, first draft: instead of having file caching handled individually by plugins, a generic module has been added in memory. - Cache can be global or associated to a profile. In the later case, client.cache can be used. - Cache are managed with unique ids (which can be any unique unicode, hash uuid, or something else). - To know if a file is in cache, getFilePath is used: if the file is in cache, its absolute path is returned, else None is returned. - To cache a file, cacheData is used with at list the source of cache (most of time plugin import name), and unique id. The method return file opened in binary writing mode (so cacheData can - and should - be used with "with" statement). - 2 files will be created: a metadata file (named after the unique id), and the actual file. - each file has a end of life time, after it, the cache is invalidated and the file must be requested again.

d660d1e5cee410bf9ac15b89ceb93543bcff0a6f SàT v0.0.2
b95550704b4f965c9dca5f6681186bf8a9b64074 SàT v0.0.3
b778622b87337785252d47d2b3c4fe3085a37ab4 SàT v0.1.0
53aa958a2d3d6451ae75610e3c6fb947d3d6f21b SàT v0.1.1
cc2afb92ab93a4c6399ca9b6cdc5224878a57a24 SàT v0.2.0
df6b9b881f0e9f335483c986b00fd58f2ed6164a SàT v0.3.0
12cfa23c6ab9235dddb2e8887eb0fe90fc98da75 SàT v0.4.0
f93e917be3f41a254a4612da22ed9fc5e0209f80 SàT v0.4.1
a090e5ee83c2c2d9d110c7516c3d74573426a97b SàT v0.5.0
008c8ccd5dcc4c47578ee7190e6823186720c864 SàT v0.5.1
21e6d11615eaeb7e03bacf4eb53e5c3c5d54ce08 0.6.0
b075c5a576ef3ce628e30b0ce02bf00ec35a3c4c 0.6.1