Which method is best for creating Threads?

[makpandian]

I know that there are two ways to create threads.
First one is extends Thread class.
Second one is Implements Runnable interface.

Which method is best for Thread application and Why?

Share your thoughts with me...

Thanking You.

[RamyaSivakanth]

As far as my knowledgee is concerned Thread using Runnable is the best one.
Because u can extend other class.
Example : Applets

[makpandian]

Thanks Ramya for sharing your thoughts with me.


But my friend told that whenever we use divide and conquer in our application,Extends Thread class is more comfortable than previous one.

Do you have any idea about it?Are you indian?

[neilcoffey]

Neither is intrinsically "better"-- which to use largely depends on what seems a more logical design for your program.

In principle, a Runnable represents what gets run, while a Thread represents how it gets run: the Thread object is where you can set things like name and thread priority, and is where you actually start the task running.

There are also other ways of running a Runnable without explicitly wrapping a thread around it: for example, the Java 5 concurrency utilities such as ThreadPoolExecutor, or SwingUtilities.invokeLater().

However, as a "shortcut", you can override the run() method on Thread. This is convenient where (a) your runnable class doesn't need to override anything else, and (b) it makes sense for you to keep the "what" code next to/coupled with the "how" code. Whether (a) and (b) are true really depends on your particular program.

Some more info I've written: constructing Threads and Runnables.

[Mrs. Deswal]

Hi,

I am also in favour of implementing Runnable interface instead of extending Thread class.

[Steve11235]

While I agree with what Neil said, I think that the focus should typically be one what is running, not how. The nice thing about implementing Runnable is that the object does not *have* to be run on a thread. You gain flexibility without losing anything.

[angryboy]

I thought I read in the api not to extend threads, and finally found that passage:

In most cases, the Runnable interface should be used if you are only planning to override the run() method and no other Thread methods. This is important because classes should not be subclassed unless the programmer intends on modifying or enhancing the fundamental behavior of the class.

from java.lang.Runnable

[Steve11235]

The JavaDoc has spoken. Word. ;-)

In this case, AB is correct in quoting the API. I just hear that at work all the time, generally about things where what Sun says really doesn't have anything to do with the problem at hand...

[toadaly]

Implementing runnable is 'better' in the sense of flexibility, but quite often, you don't care about that flexibility and just want 1 simple thing done in a different thread. In a case like that, extending Thread via an anonymous class often provides the most concise and maintainable code.

It all depends on what is meant by 'better'.

[Supamagier]

Only extend the Thread class if you want to extend the function ability of the Thread... hence the name, extend...

[jSarK0Y]

it's simply: Runnable are good for visual modules of app -- Thread are good for calculation's tasks.

[makpandian]

Thanks to all those shared your thoughts with this post..

At last,I would like to say here some thing about this thread is that it is decided that Using Runnable interface is more comfortable rather than using Thread class for Java Programming.

Thanks a lot Once again.