On Wed, Jun 19, 2013 at 01:07:29PM -0400, John Burwell wrote: > Nitin, > > If we provide any APIs for the staging/temporary area, they must be > read-only. Allowing any external manipulation of its content could cause > break in-flight transfers or cause data loss. I think we should consider the > following APIs: > > List contents including name, reference count, and size > Summary statistics for a staging area including consumed/available/total > space and timestamp of the last garbage collection operation > Force garbage collection/cleanup operation > > I think we should these are new API calls specific to the staging/temporary > area mechanism rather than trying to overload existing API calls. > > Thanks, > -John
What about creating / destroying them?
