http://cemerick.com/2006/08/30/memory-mapping-files-in-java-causes-problems/ Against all odds. Wed, 08 Feb 2012 21:48:51 +0000 hourly 1 http://wordpress.com/ http://cemerick.com/2006/08/30/memory-mapping-files-in-java-causes-problems/#comment-90 Thu, 31 Aug 2006 02:27:21 +0000 http://cemerick.com/?p=250#comment-90 That’s a cruel thing to do to such a new API, but I understand the sentiment. I do think a lot of confusion could have been avoided if they didn’t use map as the function name that returns the mapped DirectByteBuffer, so as to indicate that the operation’s behaviour is not quite what one would expect.

]]> http://cemerick.com/2006/08/30/memory-mapping-files-in-java-causes-problems/#comment-89 Thu, 31 Aug 2006 02:26:26 +0000 http://cemerick.com/?p=250#comment-89 Wow. Thanks for the info. Sun should at least @Deprecate memory mapped files if they aren’t going to fix this bug. JNI time I suppose for those that really need memory mapped files.

]]>