backend: performance improvement: now getFileInfo() and extractDetailInfo() are fully cached on disk: this means the second time the file details are requested (by anyone), you'll get a very fast response as the entire getID3::analyze() AND the info munching/formatting following that one are fully cached.
backend: performance improvement: now getFileInfo() and extractDetailInfo() are fully cached on disk: this means the second time the file details are requested (by anyone), you'll get a very fast response as the entire getID3::analyze() AND the info munching/formatting following that one are fully cached.

We use serialize()/unserialize() as that is faster than JSON_encode/decode; our backend is the only one that will access these cache files so we can pick any format: the fastest one available.

Prevention against serving 'aged data': cache files are destroyed when they prove to be outdated (i.e. when the cached 'last modified' timestamp of the original file does not match its actual 'last modified' timestamp.

Since this cache mechanism uses the same directory strucuture and file naming approach as the thumbnails, these cache files will be destroyed alongside the thumbnails on delete/move/rename.

cpojer/mootools-filemanager,cpojer/mootools-filemanager