Re:No More Callbacks: 10,000 Actors, 10,000 Threads, 10,000 ...
by pron on Wednesday October 16, 2013 @06:41PM
(#6562543)
A synchronized method would block the entire thread, but calls to ReentrantLock.lock, or any other java.util.concurrent class, can be turned from thread-blocking to fiber blocking.
Does this play well with existing JVM threading support? More specifically, if there is a call to a synchronized method inside of a fiber and another JVM thread has entered the monitor, will this block the entire fiber scheduling thread?
The reason I ask is I'd like something that plays well with legacy code.