One thing I currently thougth about is the scope of its content. By default the content is global to all users using the singleton FileSytemManager.
Though, we could use the FileSystemOptions to force VFS to create a new RamFileSystem instance.
I'm not certain how the config builder bit works, but it was simple to implement a "set" portion of the URI:
ram://[set]<path>
Which behaves like "host" does for a URL. If there is no "set", I use the global set (empty string). The URI for root directory of the global set looks like:
ram:///
Not pretty, but that's only the canonical form.
Could you explain the tradeoffs between putting the RAM set into the URI v. as an option to the configuration builder?
Thanks! --binkley
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
