VFS - Next
apply http://issues.apache.org/bugzilla/show_bug.cgi?id=33795
ram filesystem
apply http://issues.apache.org/bugzilla/show_bug.cgi?id=36047
services & svn filesystem
we need a discussion about a new name instead of "services" The idea is to have a call like
Commit commitFile = FileObject.getService(Commit.class) commitFile.process();
of
TumbnailImage thumb = FileObject.getService(TumbnailImage.class) thumb.process(); Image bi = thumb.getImage();
You get the idea?
The current name proposals are:
- serivce - getService()
- aspect - getAspect()
user api
a way to avoid to put username/password into the url.
Using a callback mechanism to get this data when needed.
progress & cancellation api
callbacks to be informed about ongoing operations (copy, move, rename, delete, copy-progress, move-progress (if between filesystems))
caching review - allow to configure fileObjects internal state cache
This is to avoid the .close() calling to get fresh data.
Sure, this might slow down alot, but if one would like have it, it should be possible.
file permissions (non-native)
(with non native code only)
figure out a way to represent file permissions and a way to modify then
browse roots
e.g. smb or local partitions (windows - c:, d:, ...)
native parts (if possible through jdic)
- filesystem notifications - to get informed about external filesystem events
- file permissions to allow fine grained setup for local files