Posted by Coder.
Jun
23
Posted by Coder.
Is OS specific interruptible I/O a Java portability headache?
…this program below does nothing visible on Solaris, but prints “hello” with Sun Java SE on Linux and Windows:
public class Foo {
public static void main(String[] args) {
Thread.currentThread().interrupt();
System.out.println(“hello”);
}
}
First impressions of this program’s behavior on Solaris roughly translate to “The hell you say!” followed by “Java is broken on Solaris!” There are a number of “symptoms” of interruptible I/O that catch users off guard and in a few cases one is led to wonder if it might be best to do without this feature whose flip side is that it allows “breaking out” of I/O operations that folks really want to be able to escape from.
There are 0 comments to this post.
Add Your Comment.
Previous Post
« Vista improvements in performance and scalability Next Post
Will Dolphin let us save the compiled code cache? »
« Vista improvements in performance and scalability Next Post
Will Dolphin let us save the compiled code cache? »