[
https://issues.apache.org/jira/browse/VFS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599578#action_12599578
]
Mario Ivankovits commented on VFS-210:
--------------------------------------
Yes!
I haven't changed the API so far and I do not plan to do so. There are just a
few changes in the contract VFS had with some of it's abstract methods in
AbstractFileObject. Nothing too serious so far.
If your code does something like this ...
FileObject fo = VFS.getManager().resolveFile("ftp://xyz/....";);
if (fo.getType().hasChildren())
{
// traverse fo
.... fo.getChildren();
}
... you should not see any changes. But you could also not expect any
performance increase as you called getType().
With the commits today you will be able to:
FileObject fo = VFS.getManager().resolveFile("ftp://xyz/....";);
// traverse fo
.... fo.getChildren();
This will no longer call getType(), not in your code nor within VFS. Thus, it
is no longer required to list the parent directory which was a real pain.
You will get a FileNotFolderException from getChildren() if the file wasn't a
directory instead.
Both modes work in parallel. It just depends on the way how you use the VFS API.
> Wrapper-Mode VFS
> ----------------
>
> Key: VFS-210
> URL: https://issues.apache.org/jira/browse/VFS-210
> Project: Commons VFS
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: Mario Ivankovits
> Assignee: Mario Ivankovits
> Fix For: 2.0
>
>
> VFS should behave more like a wrapper to the underlaying library than a full
> blown filesystem.
> This should solve the following problems:
> * access of hidden files/directories
> * access to special folders
> * speed up FTP access
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
