Hi all, Hi Lukas, I've sucessfully used continuation with non blocking IO, this is really cool. see http://weblogs.java.net/blog/forax/archive/2009/11/22/nio-server-continuation-java
But @Continuable seems odd for me. Why method need to be marked @Continuable ? What is the reason ? Is there a problem in the implementation that in order to be solved need to split method in two kinds, continuable or not ? Is it a security reason ? Because @Continuable is required, there is not way to use any external jars or even classes that already exist in the JDK like by example trying to yield in a SAX handler of an XML parser. This limitation seriously limit the usefulness of the current continuation implementation. Rémi _______________________________________________ mlvm-dev mailing list [email protected] http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
