Introduce one extra layer for the cache-folder

[joachimtingvold]

Introduce one extra layer for the cache-folder

[joachimtingvold]

(I'm just putting old "future enhancement ideas" on the paper now that we have a GitHub (-: )

[paolobenve]

I had thought about something this problem, too. I have 38k photos, and I'm afraid that some day I'm going to reach the os limit.

My idea was to implement a folder structure based on md5: calculate md4 of the path+name or of cachepath and take the first two chars of it as folder name, this way chache will be subdivide into 256 folders

[joachimtingvold]

That would make it somewhat hard to "locate" files manually?

How about using the first two characters of the album as the folder name? That would theoretically limit it to 26^2 folders (or some more if you count non-english characters), but would in reality be much less. It would also make it somewhat intuitive to locate the cached files (if you'd like to alter/manage/delete/whatnot them), as you'd only need the album name to derive the folder. In addition, this would cause all the files for the same album to be in the same folder (and not split into several folders, which would be the case in your example).

[paolobenve]

done in cacheSubDirs branch

for a given photo, the thumbnails are put in a cache subfolders identified by the first two characters of the md5 of the image path+name, the subdir is saved in the json files so that it's retrieved easily

the json files carry the cache path of every photo, so that a js call is saved