Usage differences for the "dir" action

The "dir" action has usage differences between FileStore (NS3) and ObjectStore (NS4).

Files and directories with the same name

  • FileStore: This doesn't apply with FileStore. Objects that exist in the same parent directory cannot use the same name. (For example, a file and a subdirectory that exist in the same directory cannot both be named "baseball.")
  • ObjectStore: All path names are treated independently of all other path names. Directories, generated symlinks and uploaded files that exist in the same parent can use the same name in ObjectStore. Therefore, response output for a dir action may reveal multiple entries with the same “name” attribute. To accommodate this, the accompanying “file type” attribute will differentiate each object.

Trailing slashes “/” in directory and file names

  • FileStore: This doesn't apply with FileStore. Forward slashes “/” are only supported as path separators in FileStore, so additional ones cannot be used in file/directory names.
  • ObjectStore: Trailing slashes “/” are supported for use in file and directory names in ObjectStore. Details are fully outlined in the action’s description in the NetStorage Usage API for NS4.

Periods as path objects

  • FileStore: This is not supported with FileStore. Periods are only supported as filename.extension separators.
  • ObjectStore: Path components can begin with a period (“.”). For example, “dir1/dir2/.test/one”, “dir1/dir2/./one” and “dir1/dir2/../one”. They are just considered strings. As long as the client views a filename of “.” or “..” literally, it will function properly