Cache must support locks; transaction support is not needed.
缓存必须支持锁；事务支持则不是必须的。
Stale connections should be removed from the transaction manager cache so that first invocations of transactions after the resource manager becomes available do not fail.
要把旧的连接从事务管理器的缓存中移除，这样的话，资源管理器恢复可用后的第一个事务调用就不会出错。
Sometimes you need to check a user's authentication credentials with a connection to a corporate LDAP directory or database, and the operation to cache is this transaction.
有时您需要检查一个用户连接到公司LDAP目录或数据库的认证凭证，对此进行高速缓存的操作就是这样的事务。
Neither cache lock nor cache transaction support is needed.
既不需要支持缓存锁，也不需要支持事务。
This approach supports caching within the browser cache and avoids the need to incur even a network transaction to retrieve these pieces during subsequent sessions.
这种方法支持使用浏览器缓存进行缓存，并且在随后的会话中，也不需要再使用网络事务获取这些代码部分。
As discussed earlier, with a write-behind cache, the transaction completes when the data is written to the cache, which is fast.
正如上文讨论的一样，使用写入后缓存，事务在数据写入缓存时完成，这样速度更快。
Updates to the cache occur after the database transaction has completed.
对缓存的更新发生在数据库事务完成后。
Updates to the cache and the database are wrapped in the same JTA transaction so that the cache and database are always synchronized.
对缓存和数据库的更新被包装在同一个JTA事务中，这样缓存与数据库总是保持同步的。
Softlocks cache; updates database in a transaction; updates cache after the previous transaction has completed successfully; otherwise releases the softlock.
软锁缓存；在一个事务中更新数据库；在上一个事务成功完成后更新缓存；否则释放软锁。
It works by retrieving the data row information that the reader transaction needs from the DB2 logs-usually from the log's memory cache, which is very fast.
它采用的方法是从DB 2日志(常常是从非常快速的日志内存缓存)中获取读者事务需要的数据行。
Updates database in a transaction; evicts cache before the previous transaction completes; evicts cache again for safety after the previous transaction has completed successfully or not.
在一个事务中更新数据库；在上一个事务完成前就清除缓存；为了安全起见，无论事务成功与否，在事务完成后再次清除缓存。
Updates database in a JTA transaction; updates cache in the same transaction.
在一个JTA事务中更新数据库；在同一个事务中更新缓存。
This is one of the first major pitfalls of transaction processing: ORM-based frameworks require a transaction in order to trigger the synchronization between the object cache and the database.
这是事务处理的主要陷阱之一：基于 ORM 的框架需要一个事务来触发对象缓存与数据库之间的同步。
Using ASPs is particularly important to separate the transaction logging files from the Lotus Domino data files and the Lotus Quickr cache from the Lotus Quickr data for performance reasons.
出于性能原因，使用ASP 对于将事务日志文件从LotusDomino数据文件、LotusQuickr缓存与 Lotus Quickr 数据中分离出来非常重要。
Transaction Management: the new JTA support enables the cache to participate as an XA resource in JTA transactions.
事务管理：新的JTA支持特性允许缓存在JTA事务中以XA资源的形式存在。
For example, you can pull information from a database and use an entity bean to cache the data for the duration of a transaction.
例如，您可以从数据库提取信息，并使用实体bean在事务处理期间高速缓存数据。
Transaction-aware read-write for the “transactional” cache usage.
针对“transactional”的事务感知读写。
Mobile database is mainly composed of some pacing technologies: mobile transaction processing technology, mobile query optimization technology, copy and cache technology.
移动数据库主要具有以下几种关键技术：移动事务处理技术、移动查询优化技术、复制与缓存技术。
Mobile database is mainly composed of some pacing technologies: mobile transaction processing technology, mobile query optimization technology, copy and cache technology.
移动数据库主要具有以下几种关键技术：移动事务处理技术、移动查询优化技术、复制与缓存技术。
应用推荐