AW: TrueZIP 7.2-beta-1 with NIO.2 FileSystemProvider

[Alan Bateman]

Christian Schlichtherle wrote:
>
> Hi Alan,
>
>  
>
> thanks. I'm working on the issues you found in your first email. These 
> are supposedly bugs. So yes, a user can choose to stick with the pure 
> NIO.2 API and does NOT NEED to have a compile time dependency on the 
> TrueZIP Path module. This is my objective.
>
>  
>
> However, I do not agree that a client application SHOULD NOT have a 
> compile time dependency on the TrueZIP Path module. There are some 
> features which I plan to support which simply can't be done with the 
> NIO.2 API. My primary concern is that with Paths.get(URI) you can only 
> use the URI scheme associated with the FileSystemProvider at compile 
> time - we discussed this at lengths before.
>
Okay, just mostly pointing that in the current beta that the Path that 
is returned from the FileSystem's getPath method has a few issues but 
they work if TPath objects are created directly. If applications need to 
get to provider specific features then they will of course have a 
dependency on that provider.

-Alan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/nio-discuss/attachments/20110610/e4bf7702/attachment.html