Custom cache engine for picsCache

Like the custom storage engine for cached files, allow us to customize the way picsCache gets stored. Perhaps we maintain our own (big) database of product infos and we don’t want to store it all to memory in the picsCache property. Or we ignore it with the potential of duplicated memory, which is terribly inefficient.

For example:

user.picsCache.on('updateApp', function(appid, appinfo, callback) {
	someStorageSystem.saveFile(appid + ".json", JSON.stringify(appinfo), function(err) {
		callback(err);
	});
});

user.picsCache.on('readApp', function(appid, callback) {
	someStorageSystem.readFile(appid + ".json", function(err, contents) {
		if(err) {
			callback(err);
			return;
		}

		callback(null, JSON.parse(contents));
	});
});

[DoctorMcKay]

No, the PICS cache is entirely in-memory. Appdata is used for:

• Sentry files
• Depot decryption keys
• Apptickets
• Machine IDs (if you opt for the PersistentRandom machine ID)
• Server lists
• The last cellID you connected to

[Revadike]

• Depot decryption keys

ah yes, this is what I remember.