Benedict Elliott Smith
lists at laerad.com
Mon Jul 19 07:31:08 PDT 2010
For very large directories it is useful to be able to perform a walk with
multiple threads - i abandoned this API in a project recently for that very
reason. Obviously a File.walkFileTreeConcurrently() (or similar) method
would have to error if any method result was SKIP_SIBLINGS, and accept that
TERMINATE would not effect an immediate stop.
Not sure if you're desperately keen to add such functionality, but it might
be worth considering while you're looking at it.
On 19 July 2010 15:08, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> Files.walkFileTree has accumulated a few issues that I plan to fix soon.
> Earlier this year Rémi observed that the FileVisitor methods can't throw a
> IOException and jave propagate it to the caller of Files.walkFileTree. John
> Hendrikx pointed out that the preVisitDirectory should be invoked with the
> attributes of the directory. The other one is Jon Gibbon's observation that
> using the maxDepth parameter requires opening the directory at maxDepth+1.
> All of these issues require updating the javadoc so I'd like to do them in
> one batch. Does anyone have any other issues with
> Files.walkFileTree/FileVisitor that need to be fixed while in the area?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nio-dev