Looking to use file cach now and switch to something else later. How do you build a key to handle anything you can use in a file directory and be compativle with other caches?
My data comes from files like /abc/xyz.zip and /a/b/c/xy.z.bzip2. I need to cache some of te archive contents. If I use - to replace /, I would have cache keys like the following. abc-xyz-content_part_1.txt abc-xyz-content_part_2.txt a-b-c-xy-z-content_part_1.txt a-b-c-xy-z-content_part_2.txt
With something like this, the expanded - based key could overlap with a valid file name from another directory. I might use a double dash, --, for the directory separators. Does this sound reasonable? Would it be incompatible with any of the cache backends?
I see there was an issue raised back in 2013 to make cache handle subdirectories. That will simplify the file backend, so long as it is compatible with other backends.