处理程序与AsyncTask对线程(Handler vs AsyncTask vs Thread)

 我对Android中的Handlers ， AsyncTask和Threads之间的差异有点困惑。 我在stackoverflow中阅读了不少博客和问题。 
 
 Handler是提供与UI通信的后台线程。 更新进度条例如应该通过Handler 。 使用处理程序，您具有MessagingQueues的优势，因此，如果您要安排消息或更新多个UI元素或重复任务。 
 
 AsyncTask是类似的，实际上它们使用了Handler ，但是并没有在UI线程中运行，所以它很适合于获取数据，例如获取Web服务。 稍后您可以与UI进行交互。 
 
 然而， Thread不能与UI交互，提供更多的“基本”线程，并且您错过了所有AsyncTask的抽象。 
 
 但是我想在服务中运行套接字连接。 应该在一个处理程序或线程中运行，甚至是AsyncTask ？ UI交互根本不是必需的。 在使用性能方面有什么不同吗？ 
 
 同时文件大幅改善。 

I got slightly confused about the differences between Handlers, AsyncTask and Threads in Android. I've read quite a few blogs and questions here in stackoverflow. 
 
Handler are background threads that provide you to communicate with the UI. Updating a progressbar for instance should be done via Handler. Using Handlers you have the advantage of MessagingQueues, so if you want to schedule messages or update multiple UI elements or have repeating tasks.
 
AsyncTask are similar, infact they make use of Handler, but doesn't run in the UI thread, so it's good for fetching data, for instance fetching web services. Later you can interact with the UI.
 
Thread however can't interact with the UI, provide more "basic" threading and you miss all the abstractions of AsyncTask.
 
However I would like to have a socket connection run in a service. Should this be run in a handler or a thread, or even an AsyncTask? UI interaction is not necessary at all. Does it make a difference in terms of performance which I use?
 
Meanwhile the documentation has been majorly improved.

原文：https://stackoverflow.com/questions/6964011