DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38686>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38686 Summary: Default VFS cache behavior Product: Commons Version: Nightly Builds Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: VFS AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] It's really a bug but a explanation. The default VFS cache is SoftRefFilesCache. In my process, I have a FileManipulator which is simply a singleton. This singleton create one (and only one max) instance of FileSystemManager using VFS.getManager(). This process is called every 10mn to perform a copy from a FileObject to another. In earch loop, I perform something which looks like : FIleManipulator fileManipulator = FileManipulator.getInstance(); fileManipulator.copy("tgz:http://remote/archive.tar.gz!/dir/file";, "/tmp/file"); Either the tgz:http://remote/archive.tar.gz!/dir/file has not change, in the vfs_cache directory, I have : tmp_19071_file tmp_19076_file So a copy if performed every loop and neither release which take a lot of space on the filesystem. How can I avoid this behavior ? Should I create a FileManipulator (and so a FileSystemManager) and use the same in the loop ? Do I need to define my own filesystemmanager with another FileCache system (such as NullFileCache) ? Is it possible to define another VFS cache system for the default filesystem manager got with VFS.getManager() ? Many thanks for your help. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
