> Directory provides a file abstraction. That abstraction may be
> implemented in various ways, for example, as a disk-based filesystem,
> with memory-resident datastructures, in a database, etc. Regardless
of
> how it is implemented, the abstraction refers to the storage units as
> "files", even
Matt Reynolds wrote:
Directory is currently an abstract class that claims in its javadoc that
"Directory is a flat list of files", then goes on to describe non-"flat
list of files" based implementations (JDBC, RAM, etc). Is it worthwhile
to split out Directory into a top level interface, and pos
