thread-sleep

I did some reading of other post but didn't find an exact answer to what I'm looking for, so I hope someone can give some some clarification. I have a program that will run for some time. I have some threads that run in the back ground that perform various tasks, to keep things simple let think of 3 threads. ThreadA performs a task every 10 seconds, where ThreadB does something every 30 seconds and ThreadC does something every 5 mintues. I don't use busy waiting, and put the threads to sleep for the designated times. My question is regarding a clean shut down. I have a variable that each of

I am working on app that check some of the status of phone every 5 seconds. I done it that: Thread checking = new Thread() { public void run(){ while( <<some status>> ) { <<checkstatus and do something>> Thread.sleep(5000); } } } This is bad for the battery? How can I do it in the other way? Service stop working after couple seconds. To answer your question, it depends what you are doing inside the while loop. If you are not using and waking up any "expensive" components (such as internet, bluetooth, other sensors, and screen), you should be fine. Essentially this is how the OS works in the

This question is not about designs or patterns and which to use. The heart of this question is about what is happening regarding threads and blocking. This example is to apply to any blocking method that is designed to perform the same action continuously. In this case it is a blocking read or write on a networkstream. Is there any appreciable difference behind the scenes as to threading and performance between the methods? My assumption is that each of the methods below creates a thread or uses a pooled thread. Then blocks that thread until there is data to be read. Having said that and in

My question is a bit nit-picky on definitions: Can the code below be described as "busy waiting"? Despite the fact that it uses Thread.Sleep() to allow for context switching? while (true) { if (work_is_ready){ doWork(); } Thread.Sleep(A_FEW_MILLISECONDS); } PS - The current definition for busy waiting in Wikipedia suggests that it is a "less wasteful" form of busy waiting. Any polling loop, regardless of the time between polling operations, is a busy wait. Granted, sleeping a few milliseconds is a lot less "busy" than no sleep at all, but it still involves processing: thread context switches

i have an asyncTaskProc that read some info from a DB and write it on the ui... the code works perfectcly on Android 4.0 but doesn't work on 2.3... here is the code NEW ASYNCTASK `public class IceCastPoll extends TimerTask { public IceCastPoll() { } @TargetApi(9) public void run() { new AsyncTaskProc().execute(); } }` THE ASYNCTASK implementation @TargetApi(9) class AsyncTaskProc extends AsyncTask<Void, String, Void> { List<Stream> streams=null; @Override protected void onPostExecute(Void result) { textSong =(TextView) findViewById(R.id.textViewCurrentSong); textArtist =(TextView) findViewById

This question already has an answer here: swing window getting frozen ,not displaying content 1 answer I want to create a Java application that visualizes merge sort using swing components. So far I've written this: import java.awt.event.ActionEvent; import java.awt.event.ActionListener; import java.util.Random; import javax.swing.JButton; import javax.swing.JFrame; import javax.swing.JLabel; import javax.swing.JPanel; import javax.swing.JTextArea; public class MergeSort extends JFrame { private int[] helper; private int[] heights; private JPanel mainPanel; private JTextArea[] areas; private