Hi Bernd, I'm a user rather than a developer of VFS. I have a weekend project to create a file browser in JavaFX. Prior to that I wrote an NFS provider for a company I was working for.
Concurrency/thread safety should definitely be a priority. Part of my weekend project uses a threadpool to handle a variety of different types of file operations. If there was an adapter that could adapt VFS2 calls to NIO2 calls that would be nice. But I think that rewriting all of the current providers to make them NIO2 providers would be a bit of a stretch. In your previous posting about VFS-490 you mentioned not wanting to browse JAR files as though they were directories. It would be nice if that was configurable -- I actually use that functionality and find it pretty useful. Metadata support would also be useful: http://apache-commons.680414.n4.nabble.com/vfs-File-Metadata-td739249.html Plugin download support would also be useful. One of the current problems that most users face is that the available file systems aren't downloadable from a single point. So if you encounter a URL that requires a different provider, you have to hunt around for the provider and manually install it. It would be useful VFS could simply check a registry of providers, and download the appropriate provider. It would keep the core download fairly small and make it easy for 3rd party providers to be used. The biggest challenge for most 3rd party developers is finding a way to do automated testing without installing a file system to test with. It would be interesting to find out how the NIO2 file system developers are testing their providers. Anyway, his is all probably more than you were asking for, but I hope this helps. Cheers, Mark On Wed, Oct 9, 2013 at 10:38 AM, Bernd Eckenfels <e...@zusammenkunft.net>wrote: > Dear [VFS] Developer and Contributors, > > Please excuse the spam (bcc to all emails mentioned as developers (8) or > contributors (6) in the project pom). > > The project is currently a bit in sleeping state. I raised a few concerns > and questions on the commons-dev mailinglist and wanted to direct your > attention to the list - it would also help me to provide more patches when > I know how you would prefer to solve things I raised. > > Could you maybe get ack to the list and let us know if you have any > current plans/needs with/for VFS2 and if you had looked at the recent VFS > discussions on the commons developer list. > > Currently I am mostly concerend with concurrency and atomic transactions, > but also some unclear API meanings, dirty (commented out) code and the unit > test "suite" system is somewhat confusing to use if you want to write > providers outside of the main archive (with a -tests.jar dependency only). > > I have two new providers, one which allows to project VFS on Blobs in a > JDBC table and one which simulates a virtual filesystem on top of git-style > trees. > (https://github.com/ecki/**seeburger-vfs2<https://github.com/ecki/seeburger-vfs2>). > For the former I need to implement some atomicity and concurrency (for the > content). And for the later some questions around injecting the datasource > and having additional fs operations come to mind. > > Besides that it might be time to think about > java.nio.file.spi.**FileSystemProvider > as well. > > If you feel fluent in one of the points mentioned let me know. (if too > much discussion is coming out of that we can conser moving to an google > group for those, but for now it is just a dream that that could happen :) > > What would be the quickest way for me to get acccess to the VFS wiki? > > Greetings > Bernd > -- > http://www.zusammenkunft.net > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@commons.**apache.org<dev-unsubscr...@commons.apache.org> > For additional commands, e-mail: dev-h...@commons.apache.org > >
