/packages/ThemePackageNameHere/themes/ThemeNameHere/

Thanks, I wonder why they didn't just group them with the other themes folder?

I was also confused by the image storing file locations like 4544/4545 etc

well, there is something really nice about how packages are now since they're really self-contained. Would be a pain to delete
a package if its pieces were scattered throughout the file system (although not as complicated with themes). It also means that more open write permissions only need to be set on that one packages folder.

i honestly don't fully understand the thinking behind the thinking behind the file paths though. it might be partly to limit the number of files & folders in a directory to ensure quicker file lookups, like the naming structure limits it too 10000. not sure though.

yes, depending on your operating and file system the number of files is often limited..

oh, there's a hard cutoff huh? didn't realize that. thought it was more performance related.

hmm I would have thought most servers would allow lots of images, ok, very nice cms btw, love the picnik integration

it's not about servers, it's about file systems...

performance can be an issue but with dir_index ext3 is pretty fast, even for directories with lots of files.

There are a bunch of issues you can have with lots of files in a directory.

"ls *" can give you "arguments too long"

xfs could be a good choice if you have huge directories, see this articlehttp://oss.sgi.com/projects/xfs/papers/xfs_usenix/index.html,... look for "Inability to Support Large Numbers of Files", there you find a short explanation about the problem