I have an app that needs to wait for some unknown amount of time. It must wait until several data fields are finished being populated by a server.
The server's API provides me a way to request data, easy enough...
The server's API also provides a way to receive my data back, one field at a time. It does not tell me when all of the fields are finished being populated.
What is the most efficient way to wait until my request is finished being processed by the server? Here's some pseudocode:
public class ServerRequestMethods {
public void requestData();
}
public interface ServerDeliveryMethods {
public void receiveData(String field, int value);
}
public class MyApp extends ServerRequestMethods implements ServerDeliveryMethods {
//store data fields and their respective values
public Hashtable<String, Integer> myData;
//implement required ServerDeliveryMethods
public void receiveData(String field, int value) {
myData.put(field, value);
}
public static void main(String[] args) {
this.requestData();
// Now I have to wait for all of the fields to be populated,
// so that I can decide what to do next.
decideWhatToDoNext();
doIt();
}
}
I have to wait until the server is finished populating my data fields, and the server doesn't let me know when the request is complete. So I must keep checking whether or not my request has finished processing. What is the most efficient way to do this?
wait() and notify(), with a method guarding the while loop that checks if I have all of the required values yet every time I'm woken up by notify()?
Observer and Observable, with a method that checks if I have the all the required values yet every time my Observer.Update() is called?
What's the best approach? Thanks.
If I understood you right, some other thread calls
receiveData
on yourMyApp
to fill the data. If that's right, then here's how you do it:You sleep like this:
receiveData should make a
notify
call, tounpause
thatwait
call of yours. For example like this:Both blocks will need to be "synchronized" on
this
object to be able to aquire it's monitor (that's needed forwait
). You need to either declare the methods as "synchronized", or put the respective blocks insidesynchronized(this) {...}
block.Pretty old question, but I looked for similar problem and found a solution.
At first, developer should never create a thread that will wait forever. You really have to create 'exit condition' if you are using 'while' cycle. Also, waiting for 'InterruptedException' is tricky. If another thread doesn't call yourThread.interrupt() you'll wait until program truly ends. I used java.util.concurrent.CountDownLatch so in short:
As result, 'waiting code' thread will wait until some another Thread calls 'releasing code' or will "timeout". If you want to wait for 10 fields to be populated, then use 'new CountDownLatch(10)'.
This principle is similar for 'java.util.concurrent.Semaphore' but semaphore is better for access locking and that isn't your case, indeed.
i think the most efficient method is with wait and notify. You can set a Thread into sleep with
wait()
. You can wake up the Thread from another one, e.g. your server withnotify()
to wake up.wait()
is a blocking method, you dont have to poll anything. You can also use the static methodThread.sleep(milliseconds)
to wait for a time. If you put sleep into a endless while loop checking for a condition with a continusly wait time, youll wait also.I prefer
wait()
andnotify()
, its most efficient at all.It seems like many people have been having trouble with this (myself included) but I have found an easy and sleek solution. Use this method:
This gets the current time and sets an end time (current time + time to wait) and waits until the current time hits the end time.
Use a CompletionService
http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/CompletionService.html