Mark Fortner 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?
This is easy enough to create one if there's desire :)
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?
Something that would require its own branch to land changes in would be
good to have an outline/overview architecture doc for what the changes
to make are.
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.
Seems dependent on the previous point (what exactly are the goals).
5. Has anyone considered support for virtual roots in file system URLs?
Like "home://", "documents://", "music://", etc.
Is this related to the NIO work?
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
