starting multiple threads inside a thread other than main thread

Question

0.00/5 (No votes)

See more:

Dear All,

Is it a good practice to start a thread (T2) inside another thread (T1) (other than main thread M1)?

What practical issues i will face if we go for this kind of design?

Regards,

Posted 7-May-12 5:58am

rakesh5454

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CPallini · Answer 1 · 2012-05-07T06:14:00

Solution 2

I don't see direct issues related with this choice. However you have at least two places where threads start (and possibly stop). This additional complexity, in my opinion, should be justified by an overall improvement of your design.
My two cents.

Posted 7-May-12 6:14am

CPallini

Comments

Sergey Alexandrovich Kryukov 7-May-12 19:29pm

There are no any issues related to this. My 5.
Wait a minute... why two different places (start/stop)? Yes, it could be a bad practice or just an unwanted complication, but I see no difference in in what thread this is done.
--SA

Sergey Alexandrovich Kryukov 7-May-12 19:36pm

I decided to add my own answer, which might make things clear -- please see.
--SA

Sergey Alexandrovich Kryukov · Answer 2 · 2012-05-07T13:35:00

There is practically no difference between main thread and other threads. Strictly speaking, there is not such thread as "main", this is merely some initial thread, the one where the entry point is executed. This kind of design cannot add any hassles or problems. There is only one thing: each thread should serve some purpose which should justify its use and spending resources for it existence. Of course, if a sheer purpose of a thread is to create and/or start some other thread, this hardly could be a good design, but if this thread carries some distinct functionality, why not?

—SA

Mehdi Gholam · Answer 3 · 2012-05-07T06:13:00

Solution 1

You can start thread any time you need them, the trick and problem is resource contention.

If you can use .net 4 try Tasks instead of threads.

Posted 7-May-12 6:13am

Mehdi Gholam

Comments

Sergey Alexandrovich Kryukov 7-May-12 19:31pm

I voted 4. This is not about time of creation; this is about a thread creating a thread; the trick and resource contention is also irrelevant.
Tasks? It depends. They are based on threads anyway and not always applicable. Threads are more universal.
--SA

Sergey Alexandrovich Kryukov 7-May-12 19:36pm

I just decided to add my own answer, which might make things clear -- please see.
--SA