一个 Java 小程序中的两个线程最佳实践
我见过很多这样的例子：
public class AppletName extends Applet implements Runnable {
// member variables
// run method and so on...
}
我无法弄清楚的问题是在一个小程序中使用两个线程的最佳方法是什么。我试图在 Google 上找到这个，我找到了 500 页的书籍:(，我需要一些快速的东西。
有人可以给我一些简短的例子或告诉我什么是最佳实践吗？
I have seen many examples like this:
public class AppletName extends Applet implements Runnable {
// member variables
// run method and so on...
}
The problem that I cannot figured out is what is the best way to use two threads in one applet. I tried to find this on Google I have found books with 500 pages :(, I need something quick.
Can someone give me some short example or tell me what is the best practice?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
如果它们是基于
Applet的，那么它们要么很老，要么是由相对不称职的作者编写的。把它们放回你发现它们的地方。JApplet）。If they are based on
Applet, they are either very old or written by relatively incompetent authors. Put them back where you found them.JApplet).我将使用 ExecutorService 或 ScheduledExecutorService 并将任务（例如匿名 Runnable 类）添加到线程池中。您可能会发现即使您有两个或大多数任务，您也只需要一个线程（它只是线程池的配置，您可以稍后更改）
I would use an ExecutorService or a ScheduledExecutorService and add tasks e.g. anonymous Runnable classes to the thread pool. You may find you only need one thread even though you have two or most tasks (its just a configuration of the thread pool which you can change later)
Java Applet 和线程 的示例。简短而简单。带有示例代码。
如果您有一个用于并发处理的任务池，请考虑 ExecutorService 类。
对于最佳实践，有更短的（<500 页:) 和最权威的指南 在这里。第 07 - 11 章与多线程代码相关。 （只是最佳实践和典型错误的列表）
An example of Java Applets and Threads. Short and simple. With example code.
If you have a pool of tasks for concurrent processing consider ExecutorService class.
For best practices there is a more short (<500 pages :) and the most definitive guides is here. Chapters 07 - 11 related to multithreaded code. (just a list of best practices and typical mistakes)
完善响应迅速的 Applet 和 Java GUI 应用程序需要一段时间。
你必须明白，扩展一个线程是可以的，但你用它做什么很重要。
有很多框架可供使用，如果您需要快速的东西，那么扩展线程就可以了。
您可能需要从设计角度问自己：
您的应用程序是否有多个页面/框架？
经常更新吗？ （画太多，或者只是进度条多）
是否经常需要用户输入（例如游戏控件）
如果您全部回答“是”，则考虑换行为一个线程，最好在显示线程之前启动主进程（后台）线程。
再说一次，我不知道你想实现什么目标，也许可以启发我们。
It takes a while to perfect Applet and Java GUI apps that are very responsive.
You must understand that its ok to extend a thread, but what you do with it is important.
There are many frameworks to utilize, if you need something fast, then extending a thread is fine.
You may need to ask yourself from a design perspective:
Does you app have a multiple pages / frames?
Does it updates often? (excessive paintings, or just many progress bars)
Does it require user input often (eg game controls)
If you answer Yes to all, then consider wrapping to a thread, its a good practice to start the main process (background) thread before the display thread.
again, I have no idea what you would like to achieve, perhaps enlightening us.