in the blobio c client hard linking to a temp file in /tmp implies caller can't remove the file

[jmscott]

in the blobio c client the rofs service hard links to the blobio file, eliminating the need for a copy. unfortunately, this implies the caller can't remove the link unless the caller owns the parent directory.

[jmscott]

on solution would be a symbolic link. for scripts which pull blobs fro short periods, this would be fine. for scripts need more persistent blobs, perhaps a copying version of the service. almost all the code would be inherited from the same rofs module. in other words, we would have three services: rofsl, rofss, and rofs, for hard linking, symbolic links and copying.