Balking pattern

Objects that use this pattern are generally only in a state that is prone to balking temporarily but for an unknown amount of time. If objects are to remain in a state which is prone to balking for a known, finite period of time, then the guarded suspension pattern may be preferred. ==Implementation==

Below is a general, simple example for an implementation of the balking pattern. As demonstrated by the definition above, notice how the "synchronized" line is utilized. If there are multiple calls to the job method, only one will proceed while the other calls will return with nothing. Another thing to note is the jobCompleted() method. The reason it is synchronized is because the only way to guarantee another thread will see a change to a field is to synchronize all access to it. Actually, since it is a Boolean variable, it could be left not explicitly synchronized, only declared volatile - to guarantee that the other thread will not read an obsolete cached value. public class Example { private boolean jobInProgress = false; public void job() { synchronized(this) { if (jobInProgress) { return; } jobInProgress = true; } // Code to execute job goes here // ... jobCompleted(); } void jobCompleted() { synchronized(this) { jobInProgress = false; } } } ==See also==