tag:blogger.com,1999:blog-32659296.post115627474232408185..comments2023-12-18T02:46:24.902+01:00Comments on Blackdrag's View: Groovy and Scala Multithread ActorsJochen "blackdrag" Theodorouhttp://www.blogger.com/profile/15853173707470873265noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-32659296.post-1157124016513232922006-09-01T17:20:00.000+02:002006-09-01T17:20:00.000+02:00hi jez... yes sure... there are possibilities to d...hi jez... <BR/><BR/>yes sure... there are possibilities to do that. It is not impossible. And waht I discribed is more like a draft than a implementation. I don't know about you, but I get always more ideas when implementing the stuff. Thinking it all through from the beginning to the end and coming to a superb solution si rar ;) Somewhen you are loosing the ground. Or you analyze the problem from the mathematic point, then it is ok... I was too lazy to do that here.. I hope you forgive me ;)Jochen "blackdrag" Theodorouhttps://www.blogger.com/profile/15853173707470873265noreply@blogger.comtag:blogger.com,1999:blog-32659296.post-1156360520526584222006-08-23T21:15:00.000+02:002006-08-23T21:15:00.000+02:00Luckily you can use features from java.util.concur...Luckily you can use features from java.util.concurrent to do just this (or jsr166 preview jar for lesser JVMs)...<BR/><BR/>you could wrap the method invocation in a <A HREF="http://download.java.net/jdk6/docs/api/java/util/concurrent/RunnableFuture.html " REL="nofollow">RunnableFuture</A><BR/>and use the <A HREF="http://java.sun.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html " REL="nofollow">ThreadPoolExecutor</A> as your suggested controlling mechanism.<BR/><BR/>[Doug Lea to the rescue :-) ]<BR/><BR/>ciao<BR/><BR/>jezAnonymousnoreply@blogger.com