Is there any reason why you can’t use java.nio.channels? I thought they were created for just this purpose. You get multiplexed non-blocking I/O which doesn’t rely on threads, so it scales better.
http://java.sun.com/j2se/1.4.2/docs/api/java/nio/channels/package-summary.html

I am thinking whether it is possible with any other design to avoid a new thread creations for each method call and use the same thread.
I mean for each call, its creating a new Thread, instead with any other design style is it possible to use one single thread only.(using Wait and Notify and another extra supporting Thread).

regards,
Kishore.
pra_kis @ yahoo

Basically, if you’re running into the JVM’s thread limits, you’ll have to write your own scheduler to manage execution. The coroutines won’t help performance—I’m interested in them as a way to improve the programming idioms of code that doesn’t use real threads.

I’m looking for the same sort of things.
I have been “rewriting” a scheduler to be able to explicitly manage the activation of the threads of my application, but I am facing the limit on the number of threads that a jvm can support.

Did you go any further ? I don’t know what would be the way to implement coroutine in Java and what would be the cost in term of execution time.

Thanks for your answer.

Regards.