Worker threads versus UI threads

最新推荐文章于 2025-09-04 19:07:27 发布

weixin_34310785

最新推荐文章于 2025-09-04 19:07:27 发布

阅读量60

点赞数

CC 4.0 BY-SA版权

文章标签： ui 人工智能

原文链接：https://yq.aliyun.com/articles/444988

本文探讨了富客户端应用程序中UI线程与工作线程的区别及应用方式。大多数富客户端应用采用单一UI线程来拥有和更新用户界面元素，并通过周期性创建的工作线程执行耗时任务，如数据获取等。对于具备多个顶级窗口的应用，为每个窗口分配单独的UI线程可以提升响应速度。

It’s helpful to think of a rich client application as having two distinct categories of threads: UI threads and worker threads. UI threads instantiate (and subsequently “own”) UI elements; worker threads do not. Worker threads typically execute long-running tasks such as fetching data.

Most rich client applications have a single UI thread (which is also the main application thread) and periodically spawn worker threads—either directly or using BackgroundWorker. These workers then marshal back to the main UI thread in order to update controls or report on progress.

So, when would an application have multiple UI threads? The main scenario is when you have an application with multiple top-level windows, often called a Single Document Interface (SDI) application, such as Microsoft Word. Each SDI window typically shows itself as a separate “application” on the taskbar and is mostly isolated, functionally, from other SDI windows. By giving each such window its own UI thread, the application can be made more responsive.