We don't declare any variables that might cause thread-safety issues.
我们没有定义任何会引起线程安全问题的变量。
On MVM side, we don't need to care about thread-safety, but VM communications.
从MVM的角度来看，我们不需要关注线程安全，但是需要考虑VM通讯。
While thread-safety is a term we typically use to describe code, in actuality it is about data.
尽管我们常用线程安全描述代码，但实际上它是描述数据的。
Discusses what makes a component thread-safe and how to implement thread-safety in your components.
讨论如何使组件线程安全和如何在组件中实现线程安全性。
No table-wide locking is needed (or even possible) to provide thread-safety when iterating the collection.
在对集合进行迭代时，不需要表范围的锁就能提供线程安全性。
While the JLS gives us tools with which we can make our programs thread-safe, thread-safety does not come free.
虽然JLS给了我们可以使我们的程序线程安全的工具，但线程安全也不是天上掉下来的馅饼。
It is easy to "forget" this rule, especially when reading — but doing so creates numerous risks for the thread-safety of your program.
很容易“忘记”这个规则，特别是在读取时——但是这么做可以造成很多有关程序线程安全的风险。
Not only must you pay attention to thread-safety issues, but you need to remember that a listener can mess things up for its caller in other ways, too.
不仅要注意线程安全问题，还需要记住：侦听器也可以用其他方式为它的调用者把事情搞糟。
The PHP community has stated that PHP can be used in production environments with Apache 2, as long as you use the prefork MPM to avoid thread-safety issues.
PHP社区声称，PHP可以在生产环境中与Apache2一起使用，只要您使用preforkMPM来避免线程安全性问题。
This sort of bug is commonly introduced when maintaining a class that was originally properly synchronized, but the thread-safety requirements were not fully understood by the maintainer.
这种bug通常是在维护类时引入的：这个类原来是正确同步的，但是维护人员并没有完全理解线程安全需求。
Separating the base functionality from the thread-safety Collections.synchronizedMap allowed users who needed synchronization to have it, but users who didn't need it didn't have to pay for it.
通过将基本的功能从线程安全性中分离开来， Collections.synchronizedMap允许需要同步的用户可以拥有同步，而不需要同步的用户则不必为同步付出代价。
Using ThreadLocal allows us to bypass the complexity of determining when to synchronize in order to achieve thread-safety, and it improves scalability because it doesn't require any synchronization.
使用ThreadLocal使我们可以绕过为实现线程安全而对何时需要同步进行判断的复杂过程，而且因为它不需要任何同步，所以也改善了可伸缩性。
You can use volatile variables instead of locks only under a restricted set of circumstances. Both of the following criteria must be met for volatile variables to provide the desired thread-safety.
您只能在有限的一些情形下使用volatile变量替代锁。
Thread safety also has performance implications at run time.
线程安全在运行时还具有性能牵连。
At the same time, it is insufficient to provide true thread safety, in that many common compound operations still require additional synchronization.
同时，这样仍不足以提供真正的线程安全性，许多公用的混合操作仍然需要额外的同步。
Thread safety in the current version of the framework is also questionable.
该框架的当前版本还存在线程安全问题。
Specifically, thread safety is about properly coordinating access to mutable data that is accessed by multiple threads.
具体来说，线程安全是指适当地协调对被多个线程访问的可变数据的访问。
线程安全是自动实现的。
The Participant pattern lets you make the transition from simple aspects to more complex ones such as those for transaction management, thread safety, security, etc.
Participant模式可以将简单的方面转换为更复杂的方面，如负责事务管理、线程安全、安全性等方面。
Sequel provides thread safety, connection pooling and a concise DSL for constructing database queries and table schemas.
Sequel具有线程安全，连接池等特性，同时提供了简洁的DSL用来创建数据库查询以及表方案。
Doug Cutting has posted on the topic of thread safety a couple of times.
Doug Cutting曾几次发表线程安全性的主题。
As soon as you implement a nontrivial class maintaining state between method calls, consumers of the class will want to know details about thread safety and performance.
一旦您实现了在方法调用之间保持状态的重要类，该类的使用者就会希望了解有关线程安全和性能的详细信息。
In general, strive to make your synchronized blocks as lean as possible, without harming thread safety.
一般而言，在保证线程安全的前提下要尽可能地简化同步语句。
Consider a thread-safe container class - a data structure that guarantees thread safety to its clients.
可以考虑使用一个线程安全容器类—一个保证用户操作线程安全的数据结构。
In situations where you know you need thread safety, use a thread-safe view.
在需要线程安全的情况下，请使用线程安全视图。
Analyzing the thread safety of a program that USES containers is harder with intrusive containers, because the container might be modified indirectly without an explicit call to a container member.
分析一个使用容器的程序的线程安全要比分析介入式容器更困难，因为可以无需显式调用容器的成员函数就间接修改该容器。
The set-after-write technique may be useful for state replication, but it is not enough to provide thread safety.
set-after-write技巧可能对状态复制非常有用，但还不能提供线程安全。
Any time you access a VCL UI component, you need to implement some type of thread safety measure.
任何时候你访问VCLUI组件时，您需要实现某种类型的线程安全措施。
Intrusive containers have thread safety guarantees similar to STL containers.
介入式容器具有与STL容器相似的线程安全性保证。
Intrusive containers have thread safety guarantees similar to STL containers.
介入式容器具有与STL容器相似的线程安全性保证。
应用推荐