Which direction do you have in mind here? I'd be up for helping to
build a device that makes commons-vfs act as an NIO2 file system
provider, but you might be aiming in the opposite direction.


On Wed, Jun 1, 2016 at 7:02 PM, Peter Ansell <ansell.pe...@gmail.com> wrote:
> On 2 June 2016 at 01:48, Mark Fortner <phidia...@gmail.com> wrote:
>> There was some discussion during the last release about a NIO-compatible
>> version of VFS.  This raised a few questions in my mind.
>>
>>    1. Is there a branch where this work should start?
>>    2. Are there any specific API proposals, if so where are they (or will
>>    they) be documented?  Would there be branches with specific proposal code,
>>    or a wiki?
>>    3. Does anyone have an "out of the gate" proposal? A proposed file
>>    system implementation that they're willing to contribute/collaborate on?
>>    Preferably something that's easy to test without additional server setup.
>>    Perhaps a db-based file system that could use java db?
>>    4. How would the code be organized? Would each implementation have to
>>    have its own repo? If so, this might slow down initial API development.
>>    And you always run into the danger that any API changes you make break
>>    implementing code.
>>    5. Has anyone considered support for virtual roots in file system URLs?
>>    Like "home://", "documents://", "music://", etc.
>
> Virtual roots are very simple in NIO2. They are implemented using
> FileSystemProvider with a
> META-INF/services/java.nio.file.spi.FileSystemProvider file for
> autodiscovery by java.util.ServiceLoader.
>
> https://docs.oracle.com/javase/7/docs/technotes/guides/io/fsp/filesystemprovider.html
>
> Cheers,
>
> Peter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to