Directory Name Conflict

[simoncn]

The name of the last folder is used as a persistent unique identifier for the cache file for the content directory. With your example of content directories of /Volumes/Musique-1/DSF and /Volumes/Musique-2/DSF, both cache files would be named DSF.mcache.

This name is also used as a persistent unique identifier when constructing resource URLs. For example, a file named /Volumes/Musique-1/DSF/myfolder/myfile.flac would have the resource URL http://x.x.x.x:9790/minimserver/*/DSF/myfolder/myfile.flac. These URLs are persistent and should not change if new content directories are added.

It isn't possible to use the full path to name the cache file because '/' isn't a valid character for a filename. Replacing '/' with some other character would work in some but not all cases. For example, replacing '/' with '-' would not work for content directories named /Volumes/Musique-1/DSF and/Volumes/Musique-1-DSF. Similar issues apply when constructing resource URLs.

Using the last folder name and suffixing it with [1], [2], etc. in conflict situations would not work for content directories named /Volumes/Musique-1/DSF and /Volumes/Musique-2/DSF if the user later adds a content directory /Volumes/Musique/DSF[1].

As all alternatives are more complex to explain and implement and don't work for all possible cases, the simple solution of requiring the last folder name to be unique was adopted.