Difference between revisions of "Threads"
From Suhrid.net Wiki
Jump to navigationJump to searchLine 19: | Line 19: | ||
* The thread can also go into waiting/blocked/sleeping state. e.g. waiting for an IO Resource such as a packet to arrive. In other words it is NOT ''runnable''. | * The thread can also go into waiting/blocked/sleeping state. e.g. waiting for an IO Resource such as a packet to arrive. In other words it is NOT ''runnable''. | ||
* Once run() completes the Thread goes to the dead state. You cannot call start() again on it. Of course, the thread object itself can still be used. | * Once run() completes the Thread goes to the dead state. You cannot call start() again on it. Of course, the thread object itself can still be used. | ||
+ | *''' Be careful of the Thread classes static methods such as sleep() and yield().''' They refer to the current executing thread! Do not be misled when they are invoked using a thread object. | ||
+ | * e.g. t1.sleep() will not cause Thread t1 to sleep(), it causes the current executing thread to sleep(). |
Revision as of 23:35, 8 June 2011
- Think of Thread as the "worker" and Runnable as the job.
- Define work to be done in a class that implements Runnable.
- Instantiate the thread using the runnable object. (Thread is in the new state)
- Then start() it. (Thread moves to the runnable state, eligible to run, perhaps waiting for the scheduler to run it)
class Job implements Runnable {
public void run() {
//work to be performed in a separate thread.
}
}
Job j = new Job();
Thread t = new Thread(j);
t.start();
- When thread actually runs it is in the running state.
- The thread can also go into waiting/blocked/sleeping state. e.g. waiting for an IO Resource such as a packet to arrive. In other words it is NOT runnable.
- Once run() completes the Thread goes to the dead state. You cannot call start() again on it. Of course, the thread object itself can still be used.
- Be careful of the Thread classes static methods such as sleep() and yield(). They refer to the current executing thread! Do not be misled when they are invoked using a thread object.
- e.g. t1.sleep() will not cause Thread t1 to sleep(), it causes the current executing thread to sleep().