JSR-203 Proposed Final Draft/title> </head> <body> <h1> JSR-203 Proposed Final Draft, May 2011 </h1> <h2> Table of Contents </h2> <ul> <li><a href="docs/index.html">API specification</a></li> <li><a href="#existingclasses">Changes to existing classes</a></li> <li><a href="#sincepr">Changes since Public Review</a></li> <li><a href="#sinceedr">Changes since Early Draft Review</a></li> <li><a href="#feedback">Feedback</a></li> <li><a href="#acknowledgments">Acknowledgments</a></li> </ul> <h2> <a id="existingclasses">Changes to existing classes</a> </h2> <p> java.io.File is updated with a toPath() method that returns a java.nio.file.Path object constructed from the abstract path. </p> <p> java.io.FilePermission is updated to support an action that grants the ability to read a symbolic link. </p> <p> java.util.Scanner is updated with new constructors that create a text scanner for scanning files located by a java.nio.file.Path. </p> <p> java.nio.channels.SocketChannel is updated to implement java.nio.channels.NetworkChannel and additionally defines the methods: shutdownInput(), shutdownOutput(), and getRemoteAddress(). </p> <p> java.nio.channels.ServerSocket is updated to implement java.nio.channels.NetworkChannel and additionally defines the method bind(SocketAddress,int). </p> <p> java.nio.channels.DatagramChannel is updated to implement java.nio.channels.MulticastChannel and additionally defines the methods open(ProtocolFamily) and getRemoteAddress(). </p> <p> java.nio.channels.FileChannel is updated to implement java.nio.channels.SeekableByteChannel and additionally defines new static methods to open/create the file. </p> <p> java.nio.channels.FileLock is updated to define a new protected constructor for when the lock is acquired via an AsynchronousFileChannel. FileLock is also updated to define the method acquiredBy(). </p> <p> java.nio.channels.Channels is updated with two methods for interoperation between AsynchronousByteChannel types and streams. </p> <h2> <a id="sincepr">Changes since Public Review </a> </h2> <p> BufferPoolMXBean has been moved from the java.nio package to java.lang.management so that it is in the same package as the rest of the platform's management interfaces. </p> <p> For naming consistency reasons, java.net.StandardSocketOption is renamed to StandardSocketOptions, and java.nio.file.StandardWatchEventKind to StandardWatchEventKinds. </p> <p> java.nio.file.WatchKey now defines an additional method, watchable(), to return a reference to the object for which the watch key was created. </p> <p> The parameter to java.nio.file.Path.toRealPath has been changed from a boolean to LinkOption[] so that it is consistent with the other methods. </p> <h2> <a id="sinceedr">Changes since Early Draft Review </a> </h2> <p> The Early Draft Review (EDR) proposed the java.nio.filesystems package for the file system API. This has been subsequently refined so that it is now defined in the java.nio.file package. The file system API has also undergone significant revision based on feedback and usage since it was integrated into JDK7 in 2009. </p> <p> The EDR proposed a new set of buffer classes capable of containing more than <code>Integer.MAX_VALUE</code> elements. After further examination, we decided to drop this. The primary motivation in the I/O area for large buffers is the ability to map huge files contiguously into memory. A potential solution to this problem is to examine it in conjunction with support for big arrays in the platform, something for future decisions and beyond the scope of this JSR. </p> <p> The EDR proposed java.nio.channels.AsynchronousDatagramChannel, an asynchronous channel for datagram-oriented sockets. It was included in the EDR for consistency rather than scalability reasons. After further examination we decided to drop this channel type solely for pragmatic reasons. Its specification required re-work and corresponding new development and tests. It's a class that can be re-examined again for a future JSR, maybe Java SE 8. </p> <h2> <a id="feedback">Feedback</a> </h2> <p> All feedback is welcome. The API specification included here corresponds to JDK 7 b145. </p> <p> The OpenJDK <a href="http://openjdk.java.net/projects/nio/">NIO Project</a> is where the implementation of this JSR was developed, <a href="mailto:nio-dev@openjdk.java.net"> <i>nio-dev@openjdk.java.net</i></a> is the development mailing list. </p> <p> The <a href="mailto:jsr-203-comments@jcp.org"><i>jsr-203-comments@jcp.org</i></a> mailing list may also be used to send feedback or comments. </p> <h2> <a id="acknowledgments">Acknowledgments</a> </h2> <p> Thank you to the JSR-203 Expert Group for the many conference calls and discussions that lead to the JSR-203 specification. </p> <p> In particular Mike Edwards (IBM) and Doug Lea for their guidance and time invested in the Asynchronous I/O API; Carl Quinn (formerly Google, now with Netflix), Nick Crossley (Telelogic, now IBM), Kazuhiro Kazama (NTT), and others for their time, feedback, and input to the File System API. </p> <p> Thank you to Joe Darcy, Xueming Shen, Vincent Ryan, Chris Hegarty, Tom Hawtin, Maurizio Cimadamore, Jon Gibbons, and many other colleagues and former colleagues that provided feedback and assistance. Also a big thank you to Arkadiy Sutchilin, Rajendra Gutupalli, Umashankar Ningaiah, and Sharon Zakhour for the tireless work developing tests and documentation. </p> <p> Finally, a big thank you to the community and those on the nio-dev and nio-discuss mailing lists for providing feedback on the API and implementation. Special thanks to Rémi Forax for finding many API bugs and ongoing help with reviewing both specification and implementation changes. </p> </body> </html>