Update timestamps whenever something is used and don't GC anything that's been used in the last hour. Both sides cooperate so that even if one begins to slip through, or a request comes in late, the deleting side will override the request and not delete something that's been recently referenced. The deletion can probably still be pulled out of a CAS loop so there's only one attempt, but this closes a window. Closes #83
Just pushing this out as late as possible.
Most of the time, it's because we're trying to.
Theoretically, this could avoid some overhead on large lists. Either way, we don't want to use mustEncode here because that'll crash the whole server if we run into something we can't encode. We'd rather just produce an error somewhere.
At depth=1 (default), we get the files and directories that are immediate children of the path we select. At depth=2, we get those as well as the grandchildren, separated by /