动态更新缓存页的部分。
在一个JTA事务中更新数据库；在同一个事务中更新缓存。
Updates database in a JTA transaction; updates cache in the same transaction.
软锁缓存；在一个事务中更新数据库；在上一个事务成功完成后更新缓存；否则释放软锁。
Softlocks cache; updates database in a transaction; updates cache after the previous transaction has completed successfully; otherwise releases the softlock.
当所有行处理完成之后，将完全更新缓存，并且所有相关的赋值操作符都对齐到一个合适的列。
Once all the lines have been processed, the buffer will have been completely updated and all the relevant assignment operators aligned to a suitable column.
请注意，虽然已更新缓存，但页面上显示的时间在回发事件发生之前仍将保持不变。
Note that although the cache is updated, the time displayed on the page does not change until a postback event occurs.
完成此操作的最简单方法是向服务器发送异步更新并且在处理期间，更新缓存和应用程序的 UI。
The simplest way to do this is to send an asynchronous update to the server and while that is processing, update the cache and the UI of our application.
如果缓存是一个集群，“更新缓存”的调用会将新值推送给所有副本，这通常被称为“推(push)”更新策略。
If the cache is clustered, the "updates cache" call will push the new value to all replicates, which is often referred to as a "push" update policy.
如果从这个表中更新或删除一个指南，那么需要通过发出FLUSHOPTIMIZATIONPROFILEcache语句更新缓存，使之可以被使用。
If a guideline is updated, or deleted from the table, then it is necessary to refresh the cache by issuing the FLUSH OPTIMIZATION PROFILE cache statement, so it can be used.
当一个程序写入存储，处理器仅仅只会修改缓存线，而不会更新主要的存储内容。
When a program writes to memory, the processor only modifies the line in the cache, but does not update main memory.
如同在早先章节中所说明的，您需要关闭缓存以显示更新的城市选择。
As explained in the earlier section, you need to turn off caching to get your updated city choices to display.
虽然公共基金数据每天只更新一次可以缓存，但是股票数据一直在改变。
Although mutual funds data is only updated once a day and can be cached, the stocks data keeps on changing.
在默认情况下，某些缓存对象设置为自动更新。
Some cache objects are set to automatically update by default.
即使只是添加一条注释都会提醒浏览器更新应用程序缓存。
Even adding a comment will prompt the browser to update the application cache.
每修改一个配置项时，每个实例的缓存就得到更新。
The cache of each instance must be updated whenever a configuration item is modified.
对缓存的更新发生在数据库事务完成后。
Updates to the cache occur after the database transaction has completed.
在测试或开发系统中，修改比较频繁，所以缓存更新应该设置得比较频繁。
In test or development systems, changes are frequent, so for example cache updates would likely be set to occur more frequently.
通过在DML更新前清除会话缓存，我们将时间缩短到了4分钟，全部都是将数据加载到会话缓存中花费的时间。
By clearing the session cache before DML update, we cut the time to about 4 minutes, all of which is needed by the data loading into the session cache.
在大多数情况下，不希望完全缓存那些经常更新的数据。
Most of the time, you wouldn't want to completely cache data that is being updated constantly.
例如，您可以使用每个缓存项的最长生命周期和过期时间来为需要更新数据的特定用户刷新缓存数据。
For example, you could use the maximum life and expiration time for each cached item to refresh cached data for specific users that need updated data.
这可能导致客户端更新已经从缓存中删除了的ID。
This might result in the client updating an ID that has been removed from the cache.
检测底层数据的更改，然后从缓存删除更改的数据(使其根据需要重新加载)，或者将更新的数据重新加载到缓存。
Detect changes in the underlying data, and then either evict the changed data from the cache (which will cause it to be reloaded on demand), or reload the updated data into the cache.
对缓存和数据库的更新被包装在同一个JTA事务中，这样缓存与数据库总是保持同步的。
Updates to the cache and the database are wrapped in the same JTA transaction so that the cache and database are always synchronized.
相反，在缓存中一旦进行更新操作，缓存就会跟踪脏记录列表，并定期将当前的脏记录集刷新到数据库中。
Instead, updates occur in the cache, the cache tracks the list of dirty records and periodically flushes the current set of dirty records to the data store.
从缓存中删除需要更新的页面。
Pages that need to be updated must be deleted from the cache.
该UI 的响应能力并不十分强大，但是用这种方法，我们只需在成功更新服务器时更新 UI和缓存。
The UI will not be quite as responsive, but that way, we only update it and the cache when there is a successful update to the server.
协调陈旧缓存数据的失效，以及在n层缓存中复制更新。
Coordinating the invalidation of stale cache data as well as the replication of updated across an N-tier cache.
当使用JSON将数据缓存到客户端时，系统将在用户每次单击addVehicle按钮时更新数据缓存对象。
When you cache data on the client side using JSON, you update the data caching object every time the user clicks on the Add Vehicle button.
将Hibernate的日志级别调成trace后，我们发现是更新会话缓存造成了延时。
After turning on Hibernate's log level to trace, we found it was the updating of session cache that caused the delay.
将Hibernate的日志级别调成trace后，我们发现是更新会话缓存造成了延时。
After turning on Hibernate's log level to trace, we found it was the updating of session cache that caused the delay.
应用推荐