blob: 8aa2597344b3cbc6874a1da9bbb7fc4412fc7878 [file] [log] [blame]
<?xml version="1.0"?>
<document>
<properties>
<title>Commons Virtual File System</title>
<author email="jstrachan@apache.org">James Strachan</author>
</properties>
<body>
<section name="Commons Virtual File System">
<p>
Commons VFS provides a single API for accessing
various different file systems. It presents a uniform view of
the files from various different sources, such as the files on
local disk, on an HTTP server, or inside a Zip archive.
</p>
<p>Some of the features of Commons VFS are:</p>
<ul>
<li>
A single consistent API for accessing files of different
types.
</li>
<li>Support for numerous
<a href="filesystems.html">file system types</a>.
</li>
<li>
Caching of file information. Caches information in-JVM,
and optionally can cache remote file information on the
local file system.
</li>
<li>Event delivery.</li>
<li>
Support for logical file systems made up of files from
various different file systems.
</li>
<li>
Utilities for integrating Commons VFS into applications,
such as a VFS-aware ClassLoader and URLStreamHandlerFactory.
</li>
<li>A set of VFS-enabled
<a href="anttasks.html">Ant tasks</a>.
</li>
</ul>
</section>
<section name="News">
<p>2005-07-05 - imario@apache.org: RC2 - includes multi-threading fixes for ftp and webdav</p>
<p>2005-06-29 - imario@apache.org: RC1</p>
<p>2005-06-19 - imario@apache.org: Again refactored filename parsing. sftp now accepts files with space in their filename</p>
<p>2005-05-24 - imario@apache.org: Moved VFS out of sandbox into proper. What a great day!</p>
<p>2005-05 - imario@apache.org: Find the "How to setup a VFS Testserver" documentation in the developer area.</p>
<p>2005-03 - imario@apache.org: easier configuration for plugins - see api section for details</p>
<p>2005-03 - imario@apache.org: The filename parsing and api has changed.
<ul>
<li>Now it is needed to encode the '%' sign using '%25'</li>
<li>It is no longer needed to encode the '!' sign when using nested archives (tar, jar, ...).<br />
Now you <u>can</u> encode it if you would like to use it in your filename</li>
<li>It is no longer needed to double-encode the filename when using layered names. <code>tar:tar:file:///</code></li>
<li>Depending on the filesystem special characters in your filename could automatically be encoded</li>
<li><code>FileName.resolveName(...)</code> has been moved to <code>FileSystemManager.resolveName(...)</code></li>
</ul>
</p>
</section>
</body>
</document>