例如，当写入一个文件的时候，这个文件的长度和最后修改时间都要在元数据缓存器里面更新。
For example, when we write to a file, the new length and the last modification timestamp are updated in the metadata cache.
元数据缓存器将目录和文件的路径名称保存为键，将元数据保存为值（如文件长度、最后修改时间、标记该条目是文件还是目录等）。
The metadata cache contains the full path names of directories and files as keys and metadata (e.g. file length, last modification date, and whether the key is a file or a directory) as values.
更准确地说，如果缓存从服务器可见，可以看到(或修改)其所有内容，则任何应用程序都可以查找JNDI中的缓存。
More precisely, any application can lookup any cache in JNDI if the cache is accessible from that server and then see (or modify) all of its contents.
通过把该数据结构的两个元素分离到两条不同的高速缓存线路，一条高速缓存线路的修改就不会导致再次从存储器读入另外一条高速缓存线路。
By separating the two elements of the structure into two different cache lines, modification of one cache line does not cause another cache line to be read in again from the memory.
当一个程序写入存储，处理器仅仅只会修改缓存线，而不会更新主要的存储内容。
When a program writes to memory, the processor only modifies the line in the cache, but does not update main memory.
请记住，如果把过期日期设置为很长时间以后，那么即使已经修改了内容，浏览器仍然会使用缓存的内容。
Remember that if you use far future expiration dates, browsers will still cache your content even when you have changed it.
当缓存管理器与中央服务器重新连接时，系统重建客户机修改日志，使所有的文件系统更新对客户机都可用。
When the cache manager reconnects to the central servers, the system reintegrates the client modification log, making all file system updates available to the client.
如果用户已修改她的通讯簿，时间戳可确保新的UR l不匹配，缓存的响应，并在浏览器将请求更新的地址簿条目。
If the user has modified her address book, the timestamp ensures the new URL doesn't match the cached response, and the browser will request the updated address book entries.
有些节点被当做内联缓存用来改善VM性能，这使得垃圾收集器要进行修改，忽略掉这部分内联缓存对象。
Some nodes were used as inline cache to improve VM performance. This change ignore such inline cache objects to mark on GC.
浏览器在首次访问这些文件时会缓存它们，所以浏览器两次下载了这些文件：首次访问时以及修改文件之后。
These files are cached by the browser after they are first accessed so the number of times the browser downloads the file is twice: once when it is first accessed, and once after it is modified.
对于HTTP缓存，在出现可能修改资源的服务器端状态的资源交互时，缓存项将失效。
In the case of HTTP caching, the cache entries are invalidated in case an interaction with the resource occurs that potentially modifies the server side state of the resource.
过了这个时间，缓存器就会向源服务器发送请求，检查文档是否被修改。
After that time, caches will always check back with the origin server to see if a document is changed. Expires headers are supported by practically every cache.
到达MXML的所有请求都通过Flex编译器进行处理，该编译器编译MXML并生成s WF，然后将其高速缓存，直到它被修改并最终交付给浏览器为止。
All requests that come to MXML are processed through the Flex compiler, which compiles MXML and generates SWF, and caches until it is modified and finally delivered to the browser.
到达MXML的所有请求都通过Flex编译器进行处理，该编译器编译MXML并生成s WF，然后将其高速缓存，直到它被修改并最终交付给浏览器为止。
All requests that come to MXML are processed through the Flex compiler, which compiles MXML and generates SWF, and caches until it is modified and finally delivered to the browser.
应用推荐