be7z4kuQmr3AZYab7jnrAJ 2010-02-17T21:25:28-06:00 0 984781 1 false 161077 be7z4kuQmr3AZYab7jnrAJ 1 3 be7z4kuQmr3AZYab7jnrAJ dDMk5-erOr34JreJe5aVNr 1 Accepted 0

Create remote distributor

2010-08-24T08:27:05-05:00 6.0 6.0 None 0.0 0.0 be7z4kuQmr3AZYab7jnrAJdppdppdpp be7z4kuQmr3AZYab7jnrAJdppdppdpp be7z4kuQmr3AZYab7jnrAJ 2010-02-17T21:29:51-06:00 0 984791 3 false 161077 be7z4kuQmr3AZYab7jnrAJ 3 3 be7z4kuQmr3AZYab7jnrAJ dDMk5-erOr34JreJe5aVNr 1 Accepted 0

Support for a Listener registration with Workers

2010-08-24T08:27:05-05:00 None 0.0 0.0 be7z4kuQmr3AZYab7jnrAJdppdppdpp be7z4kuQmr3AZYab7jnrAJdppdppdpp be7z4kuQmr3AZYab7jnrAJ 2010-02-25T19:05:07-06:00 Right now the future and continue mechanisms for getting answers from workers is not friendly to workers themselves. Fix this. 0 1019557 5 false 161077 be7z4kuQmr3AZYab7jnrAJ 5 3 be7z4kuQmr3AZYab7jnrAJ dDMk5-erOr34JreJe5aVNr 1 Accepted 0

Deal with continue and future on Worker thread

2010-08-24T08:35:15-05:00 None 0.0 0.0 be7z4kuQmr3AZYab7jnrAJdppdppdpp be7z4kuQmr3AZYab7jnrAJdppdppdpp 2010-03-30T09:57:54-05:00 Using Thread.sleep in concurrency-aware test cases may lead to failures due to too low values. Using a Latch (Java concurrent API) or a Conductor (ScalaTest) might help. 0 1188951 8 false 161077 8 3 b3bGMs4nur3RAbeJe5aVNr dDMk5-erOr34JreJe5aVNr 0 New 0

Replace Thread.sleep in test cases

2010-09-17T04:42:57-05:00 0.0 0.0 None 0.0 0.0 b3bGMs4nur3RAbeJe5aVNrhseebergerhseebergerHeiko Seeberger