Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When we should use threads in our application. In other words, when should I convert a single threaded application to multi-threaded application.
Being a developer, I think the task which is preventing to your application to run smoothly. That task can be handled by a thread. Like we are the getting GPS data Continuously.
I think, there are other more reasons to create thread in your application. Please share your opinion.
Thanks.
Reasons I can think of off the top of my head ( and I’m sure there are more ) are :
1. Offloading a batch of work to a worker thread so your program can either continue responding to user input or so you can carry on running other code that doesn’t rely on that work.
2. Handling I/O particularly server and network communication where the response time is variable or unknown.
3. Parallel processing of data where you can sub-divide the work down into discrete non-dependant units of work
4. Timer related work i.e ‘every 500ms check if x has changed’
However, switching to multi-threaded or concurrent programming is not without it’s pitfalls particularly if those threads need to access shared data hence the number of questions on SO about mutexes and thread synchronisation!