Talk:Non-blocking I/O (Java)

This is an old revision of this page, as edited by ZooFari (talk | contribs) at 03:47, 11 November 2009 (Adding WikiProject Java assessments per request (Mistake?) using AWB). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Latest comment: 17 years ago by DanielPitts in topic dead link - New I/O APIs - description of New I/O
WikiProject iconJava Unassessed
WikiProject iconThis article is within the scope of WikiProject Java, a collaborative effort to improve the coverage of Java on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
???This article has not yet received a rating on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.

Can you add some details about the difference between java.io.* and java.nio.* Jgold03 01:20, 27 March 2006 (UTC)Reply

maybe this is about what the link pointed to: http://java.sun.com/developer/technicalArticles/releases/nio/index.html
--212.202.41.193 20:19, 30 April 2007 (UTC)Reply

In "Copying NIO Buffers", Method 1 is flawed. The buffer2 object is completely lost after executing "buffer2 = buffer1;". After completing the execution, buffer2 points actually to buffer1.

I think the whole Copying NIO Buffers is a pointless section anyway. I suggest removing it. Actually, I'll just remove it and if someone thinks it should be re-added, we'll re-add a valid version. DanielPitts (talk) 19:11, 15 January 2008 (UTC)Reply

Last two points of "Some Usage Information for NIO Buffers" are completly wrong. NIO buffers don't block. get() into array larger than remaining() throws BufferUnderflowException instead. get into an array behind read only buffer will proceed as usual - read only buffer is just a wrapper, but never gives its clients the underlaying array anyway. —Preceding unsigned comment added by 192.9.112.196 (talk) 07:55, 12 December 2007 (UTC)Reply

You are right, blocking NIO was nonsense. Removed.