Working on an internal project that required writing lots of files to a WebDav server I spent an entire week screwing around with Commons VFSs webdav implementation. I gave up and wrote a cute wrapper around Jackrabbits Webdav HTTP Client methods which worked much better :)
Looks like the new NIO stuff in JDK7 has a Virtual File System SPI that might be interesting to have a look at. James On Sat, Mar 6, 2010 at 4:37 PM, Christian Catchpole <[email protected] > wrote: > Hmm.. it appears to be a client perspective API. "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." > I'll look at it though, and see what it contains. > > There seems to be lots of NFS clients around, as this is the common > use case. > > On Mar 6, 9:40 am, Mark Fortner <[email protected]> wrote: > > You might try Apache Commons VFS which supports a large number of file > > systems including WebDAV. WebDAV volumes are mountable via the Windows > File > > Manager as well as from OS X File Manager and the Nautilus File Manager > in > > Linux. > > > > Hope this helps, > > > > Mark > > > > On Fri, Mar 5, 2010 at 3:22 PM, Christian Catchpole < > [email protected] > > > > > > > > > wrote: > > > I have been pondering adding a "virtual file system" to one of my > > > projects. The idea is that I have data in a managed store which could > > > be represented as files. Also you could add files to the store by > > > dropping the files into the drive. I'm trying to avoid the manual > > > syncing of a real file system. > > > > > Creating the native bridge sounds painful and would be different on > > > each platform. An FTP or SSH server could work but this is still > > > clunky. > > > > > So this got me to thinking about network file systems. I could create > > > a server connector in Java. I can see there are a bunch of projects > > > around that do this. Mostly university projects and they have various > > > licenses. But there seem to be a range of different protocols, and > > > each have their own implications of features, which ports they use and > > > which OSes support them. Plus, I assume it's a "one server per IP" > > > proposition (not like a web server where you can just change to port > > > 8080 if 80 is in use). > > > > > Does anyone have experience in this space and can offer any > > > recommendations? > > > > >http://en.wikipedia.org/wiki/Network_File_System_(protocol)< > http://en.wikipedia.org/wiki/Network_File_System_%28protocol%29> > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "The Java Posse" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<javaposse%[email protected]> > <javaposse%2bunsubscr...@googlegroups .com> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/javaposse?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
