"To take advantage of this feature, the directory marker objects must also be created to represent the appropriate directories. The following additional objects need to be created. A good convention would be to create these as zero- or one-byte files with a Content-Type of application/directory."
So that's how we implemented things in Horizon; to expect those pseudo-folder objects and use those to allow traversal down into a structure. Unfortunately that doesn't play so nice with the *other* method of handling pseudo-folders which is basically to not use the "delimiter" argument on the API and just show everything, slashes and all.
At present I'm not aware of a good compromise between the two, so we erred on the side of the recommended practice in swift's docs. Suggestions are welcome.
In swift's docs (http:// docs.openstack. org/trunk/ openstack- object- storage/ developer/ content/ pseudo- hierarchical- folders- directories. html), it actually says that you must create 0-byte objects with type "application/ directory" if you intend to use the pseudo-folder feature:
"To take advantage of this feature, the directory marker objects must also be created to represent the appropriate directories. The following additional objects need to be created. A good convention would be to create these as zero- or one-byte files with a Content-Type of application/ directory. "
So that's how we implemented things in Horizon; to expect those pseudo-folder objects and use those to allow traversal down into a structure. Unfortunately that doesn't play so nice with the *other* method of handling pseudo-folders which is basically to not use the "delimiter" argument on the API and just show everything, slashes and all.
At present I'm not aware of a good compromise between the two, so we erred on the side of the recommended practice in swift's docs. Suggestions are welcome.