[jboss-cvs] JBossAS SVN: r77585 - projects/docs/enterprise/4.3/Cache/Cache_FAQ/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Aug 28 02:18:46 EDT 2008
Author: xhuang at jboss.com
Date: 2008-08-28 02:18:46 -0400 (Thu, 28 Aug 2008)
New Revision: 77585
Modified:
projects/docs/enterprise/4.3/Cache/Cache_FAQ/zh-CN/Cache_Frequently_Asked_Questions.po
Log:
update
Modified: projects/docs/enterprise/4.3/Cache/Cache_FAQ/zh-CN/Cache_Frequently_Asked_Questions.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_FAQ/zh-CN/Cache_Frequently_Asked_Questions.po 2008-08-28 06:18:30 UTC (rev 77584)
+++ projects/docs/enterprise/4.3/Cache/Cache_FAQ/zh-CN/Cache_Frequently_Asked_Questions.po 2008-08-28 06:18:46 UTC (rev 77585)
@@ -5,13 +5,13 @@
"Project-Id-Version: Cache_Frequently_Asked_Questions\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-05-30 03:54+0000\n"
-"PO-Revision-Date: 2008-08-25 16:12+1000\n"
+"PO-Revision-Date: 2008-08-28 16:14+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
-"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KAider 0.1\n"
+"X-Generator: KBabel 1.11.4\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
#. Tag: title
@@ -1266,13 +1266,13 @@
#: Cache_Frequently_Asked_Questions.xml:1049
#, no-c-format
msgid "JBoss Cache - Pojo Cache"
-msgstr ""
+msgstr "JBoss Cache - Pojo Cache"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1055
#, no-c-format
msgid "What is PojoCache?"
-msgstr ""
+msgstr "PojoCache 是什么？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1059
@@ -1288,7 +1288,7 @@
"relationship behind the scene. During replication mode, it performs fine-"
"granularity (i.e., on a per-field basis) update, and thus has the potential "
"to boost cache performance and minimize network traffic."
-msgstr ""
+msgstr "PojoCache（目前作为 TreeCache 的子类实现）是一个细颗粒度字段级别的复制和事务性 POJO（Plain Old Java Object）缓存。POJO 意味着：1）在本地和复制缓存模式下，自动管理客户端的对象映射和关系；2）提供对 \"aspectized\" POJO 间的继承关系的支持。通过 JBossAop 里的动态 AOP，它可以把复杂的对象映射到缓存库里，在后台保留和管理对象的关系。在复制模式下，它执行细颗粒度的更新（如基于每个字段），因此能够提高缓存性能并降低网络负载。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1073
@@ -1300,13 +1300,13 @@
"has been put in PojoCache (by calling putObject, for example), then any get/"
"set method will be intercepted by PojoCache to provide the data from the "
"cache."
-msgstr ""
+msgstr "从用户的角度来看，一旦你的 POJO 由缓存来管理，所有的缓存操作都将是透明的。因此，所有普通的虚拟机内的 POJO 方法模式都仍将保留以便使用。例如，如果 POJO 已经放入了 PojoCache（如通过调用 putObject），那么任何的 get/set 方法将被 PojoCache 拦截以提供缓存里的数据。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1086
#, no-c-format
msgid "What's the relationship between PojoCache and TreeCacheAop classes?"
-msgstr ""
+msgstr "PojoCache 和 TreeCacheAop 类是什么关系？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1090
@@ -1315,7 +1315,7 @@
"Since release 1.4, we have created a new class called PojoCache (to better "
"reflect the cache nature). The old implementation TreeCacheAop has been "
"deprecated."
-msgstr ""
+msgstr "从 1.4 版本开始，我们创建了一个新的类 PojoCache（以便更好地反映该缓存的性质）。旧的 TreeCacheAop 已经被取消了。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1098
@@ -1970,7 +1970,7 @@
msgid ""
"Why can't I use <literal>org.jboss.cache.eviction.LRUPolicy</literal> for "
"PojoCache as well?"
-msgstr ""
+msgstr "我为什么不能也把 <literal>org.jboss.cache.eviction.LRUPolicy</literal> 用于 PojoCache？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1697
@@ -1980,6 +1980,8 @@
"AopLRUPolicy</literal> ) because AOP has its eviction algorithm, although is "
"LRU but has totally different notion of an \"object\", for example."
msgstr ""
+"对于 PojoCache 来说，你将需要使用 <literal>org.jboss.cache.aop.eviction."
+"AopLRUPolicy</literal>。因为 AOP 有自己的 eviction 算法，虽然它也是 LRU，但具有和对象完全不同的标记。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1708
@@ -1987,13 +1989,13 @@
msgid ""
"Does JBoss Cache's implemented LRU eviction policy operates in replication "
"mode?"
-msgstr ""
+msgstr "JBoss Cache 的 LRU eviction 策略应用于复制模式吗？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1714
#, no-c-format
msgid "Yes and no. :-)"
-msgstr ""
+msgstr "可以说是，也可以说不是。：）"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1716
@@ -2006,7 +2008,7 @@
"returns null), it should get it from the other data source and re-populate "
"the data in the cache. During this moment, the node content will be "
"propagated and the cache content will be in sync."
-msgstr ""
+msgstr "LRU 策略只用于本地模式。也就是说，只在本地剔除节点。这可能导致缓存内容临时地不同步。但当用户试图从被剔除的节点获取缓存内容并发现它是空值时（如 <literal>get</literal> 返回 null），用户应该从其他数据源获取数据并在缓存里重新填充这些内容。此时，内容将在节点间传递，缓存内容又会同步了。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1727
@@ -2017,7 +2019,7 @@
"your use case, you can set multiple cache instances to have their own "
"eviction policy (which are applied locally) or just have selected instances "
"with eviction policies activated."
-msgstr ""
+msgstr "然而，你仍然可以用 <literal>REPL_SYNC</literal> 或 <literal>REPL_ASYNC</literal> 缓存模式来运行 eviction 策略。根据需要，你可以使多个缓存实例具有自己的 eviction 策略（在本地应用）或者只激活某些实例的 eviction 策略。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1738
@@ -2026,13 +2028,13 @@
"Also note that, with cache loader option, a locally evicted node can also be "
"persisted to the backend store and a user can retrieve it from the store "
"later on."
-msgstr ""
+msgstr "也请注意，如使用 cache loader 选项，本地剔除的节点也可以持久化到后台数据库里，以后用户可以从中提取它。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1747
#, no-c-format
msgid "Does JBoss Cache support <literal>Region</literal> ?"
-msgstr ""
+msgstr "JBoss Cache 支持 <literal>Region</literal>？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1754
@@ -2042,6 +2044,8 @@
"eviction policy parameters (e.g., <literal>maxNodes</literal> or "
"<literal>timeToIdleSeconds</literal> )"
msgstr ""
+"是的。JBoss Cache 具有 region 标记，用户可以配置 eviction 策略的参数（如 <literal>maxNodes</literal> 或 "
+"<literal>timeToIdleSeconds</literal>）。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1762
@@ -2053,7 +2057,7 @@
"separate regions. But note that you can configure the region "
"programmatically now, i.e., everything has to be configured through the xml "
"file."
-msgstr ""
+msgstr "JBoss Cache 的 region 构成树型分层结构的一部分，如全限定名（<literal>FQN</literal>）。例如，用户可以把 <literal>/org/jboss</literal> 和 <literal>/org/foocom</literal> 定义为两个独立的 region。但请注意，目前你还不能在程序里配置 region，也就是说一切都得通过 XML 文件进行配置。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1779
@@ -2061,25 +2065,25 @@
msgid ""
"What are the <literal>EvictionPolicyConfig</literal> tag parameters for "
"<literal>org.jboss.cache.eviction.LRUPolicy</literal> ?"
-msgstr ""
+msgstr "<literal>org.jboss.cache.eviction.LRUPolicy</literal> 的 <literal>EvictionPolicyConfig</literal> 标签的参数是什么？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1789
#, no-c-format
msgid "They are:"
-msgstr ""
+msgstr "它们是："
#. Tag: title
#: Cache_Frequently_Asked_Questions.xml:1793
#, no-c-format
msgid "Parameters"
-msgstr ""
+msgstr "参数"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1798
#, no-c-format
msgid "wakeUpIntervalInSeconds"
-msgstr ""
+msgstr "wakeUpIntervalInSeconds"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1800
@@ -2087,13 +2091,13 @@
msgid ""
"Interval where the clean up thread wakes to process the sitting queue and "
"sweep away the old data."
-msgstr ""
+msgstr "唤醒 Clean up 线程来处理 sitting 队列并清除旧数据。"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1806
#, no-c-format
msgid "region"
-msgstr ""
+msgstr "region"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1808
@@ -2101,31 +2105,31 @@
msgid ""
"A area where each eviction policy parameters are specified. Note that it "
"needs a minimum of <literal>/_default</literal> region."
-msgstr ""
+msgstr "每个 eviction 策略参数所应用的区域。请注意，你最少需要一个 <literal>/_default</literal> region。"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1816
#, no-c-format
msgid "maxNodes"
-msgstr ""
+msgstr "maxNodes"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1818
#, no-c-format
msgid "Max number of nodes allowed in the eviction queue. 0 means no limit."
-msgstr ""
+msgstr "eviction 队列里允许的节点的最大数目。0 表示无限制。"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1824
#, no-c-format
msgid "timeToLiveInSeconds"
-msgstr ""
+msgstr "timeToLiveInSeconds"
#. Tag: entry
#: Cache_Frequently_Asked_Questions.xml:1826
#, no-c-format
msgid "Age (in seconds) for the node to be evicted in the queue. 0 denotes no limit."
-msgstr ""
+msgstr "队列里节点被剔除前停留的时间（秒）。0 表示无限制。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1838
@@ -2134,6 +2138,8 @@
"I have turned on the eviction policy, why do I still get \"out of memory"
"\" (OOM) exception?"
msgstr ""
+"我已经启用了 eviction 策略，但为什么还遇到 \"out of memory"
+"\" (OOM) 异常？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1844
@@ -2148,6 +2154,8 @@
"the VM heap size, you can also reduce the <literal>wakeUpIntervaleInSeconds</"
"literal> so the timer thread processes the queue more frequently."
msgstr ""
+"当缓存速度超出了 eviction 策略处理定时器的速度时，OOM 就会出现。Eviction 策略处理程序将每隔<literal>wakeUpIntervalInSeconds</literal> 秒被唤醒并处理 eviction 队列。队列的大小目前被固定为 20000。所以，当队列满了，它将创建积压，除非被 eviction 定时器捕获，否则 OOM 将出现。要解决这个问题，出了增加 VM 的堆大小，你也可以减少 <literal>wakeUpIntervaleInSeconds</"
+"literal>，让定时器线程更加频繁地进行处理。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1858
@@ -2155,19 +2163,19 @@
msgid ""
"We will also externalize the queue size so it will be configurable in the "
"next release."
-msgstr ""
+msgstr "在以后的版本里，我们也将扩充队列的大小，使其成为可配置的参数。"
#. Tag: title
#: Cache_Frequently_Asked_Questions.xml:1866
#, no-c-format
msgid "Cache Loaders"
-msgstr ""
+msgstr "Cache Loader"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1873
#, no-c-format
msgid "What is a CacheLoader?"
-msgstr ""
+msgstr "什么是 CacheLoader？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1877
@@ -2178,7 +2186,7 @@
"data is not in the cache, and when modifications are made to data in the "
"cache the CacheLoader is called to store those modifications back to the "
"store."
-msgstr ""
+msgstr "CacheLoader 是 JBossCache 和持久性数据库的连接。当数据不在缓存里时，JBossCache 调用 CacheLoader 来从数据源获取数据，而当缓存里的数据有变到时，它调用 CacheLoader 来把这些变到存回数据库里。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1884
@@ -2190,7 +2198,7 @@
"data is evicted, in order to provide fast access to frequently accessed "
"data. This is all configured through XML, and the programmer doesn't have to "
"take care of loading and eviction."
-msgstr ""
+msgstr "配合 eviction 策略的使用，带有 CacheLoader 的 JBossCache 允许用户维护用于大型后台数据库的有界缓存。被频繁使用的数据从数据库提取到缓存里，而最少使用的数据则被剔除，这是为了提供对被频繁使用的数据的快速访问。这都可以通过 XML 进行配置，程序员不需要担心数据的加载和剔除。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1893
@@ -2198,7 +2206,7 @@
msgid ""
"JBossCache currently ships with several CacheLoader implementations, "
"including:"
-msgstr ""
+msgstr "JBossCache 目前带有几个 CacheLoader 实现，如："
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1900
@@ -2209,6 +2217,8 @@
"subdirectories etc. Attributes of a node are mapped to a file <literal>data</"
"literal> inside the directory."
msgstr ""
+"FileCacheLoader：这个实现使用文件系统来存储和提取数据。JBossCache 节点映射到目录，而子节点则对应子目录。节点的属性映射为目录里的 <literal>data</"
+"literal> 文件。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1911
@@ -2221,6 +2231,8 @@
"url=\"http://www.sleepycat.com/jeforjbosscache\">commercial license from "
"Sleepycat </ulink> ."
msgstr ""
+"BdbjeCacheLoader：这个实现基于 Sleepycat 的 Java 版本的数据库，这是一个高效的事务性数据库。对于整个数据库，它使用单个文件。请注意，如果你将 Sleepycat 的 CacheLoader 和 JBoss Cache 一起使用并希望分发自己的产品，你将需要从 Sleepycat 获得<ulink "
+"url=\"http://www.sleepycat.com/jeforjbosscache\">商业性的许可证书</ulink>。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1923
@@ -2228,7 +2240,7 @@
msgid ""
"JDBCCacheLoader: this implementation uses the relational database as the "
"persistent storage."
-msgstr ""
+msgstr "JDBCCacheLoader：这个实现把关系型数据库用作持久性存储。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1929
@@ -2236,19 +2248,19 @@
msgid ""
"ClusteredCacheLoader: this implementation queries the rest of the cluster, "
"treating other servers' in-memory state as a data store."
-msgstr ""
+msgstr "ClusteredCacheLoader：这个实现查询群集的其他部分，把其他服务器的内存状态当作数据库。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1935
#, no-c-format
msgid "And more. See the documentation for more details."
-msgstr ""
+msgstr "关于其他的实现，请参考相关文档。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1944
#, no-c-format
msgid "Can writing to CacheLoaders be asynchronous?"
-msgstr ""
+msgstr "对 CacheLoader 的写入可以是异步的吗？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1948
@@ -2257,13 +2269,13 @@
"As of JBossCache 1.2.4, yes. Set the CacheLoaderAsynchronous property to "
"true. See the JBossCache documentation for a more detailed discussion. By "
"default though, all cache loader writes are synchronous and will block."
-msgstr ""
+msgstr "到 JBossCache 1.2.4 为止，可以。请把 CacheLoaderAsynchronous 属性设置为 true。详情请参考 JBossCache 的文档。但在缺省情况下，所有对 cache loader 的写入都是同步的且可能阻塞。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1958
#, no-c-format
msgid "Can I write my own CacheLoader ?"
-msgstr ""
+msgstr "我可以编写自己的 CacheLoader 吗？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1962
@@ -2273,12 +2285,15 @@
"CacheLoader</literal> . It is configured via the XML file (see JBossCache "
"and Tutorial documentation)."
msgstr ""
+"可以。CacheLoader 是一个实现 <literal>org.jboss.cache.loader."
+"CacheLoader</literal> 的类。它可以通过 XML 文件来配置（请参考 JBossCache "
+"教程）。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1973
#, no-c-format
msgid "Does a CacheLoader have to use a persistent store ?"
-msgstr ""
+msgstr "CacheLoader 必须使用持久性存储吗？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1977
@@ -2289,7 +2304,7 @@
"fetches contents from the web. Note that an implementation of CacheLoader "
"may not implement the 'store' functionality in this case, but just the "
"'load' functionality."
-msgstr ""
+msgstr "否，例如 CacheLoader 可以从启用 webdav 的 web 服务器中获取数据。另外一个例子就是缓存代理服务器，它也从 web 提取数据。请注意，此时 CacheLoader 的实现可以仅仅实现 'load' 功能而不实现 'store' 功能。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:1989
@@ -2345,7 +2360,7 @@
#: Cache_Frequently_Asked_Questions.xml:2040
#, no-c-format
msgid "How do I configure JBossCache with a CacheLoader?"
-msgstr ""
+msgstr "我怎样配置带有 CacheLoader 的 JBossCache？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2044
@@ -2354,13 +2369,13 @@
"Through XML: both the fully-qualified classname of the CacheLoader and its "
"configuration string have to be given. JBossCache will then instantiate a "
"CacheLoader. See JBossCache documentation for details."
-msgstr ""
+msgstr "通过 XML：CacheLoader 的全限定名和配置串都必须被指定。然后 JBossCache 将初始化 CacheLoader。详情请参考 JBossCache 文档。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2054
#, no-c-format
msgid "Do I have to pay to use Sleepycat's CacheLoader?"
-msgstr ""
+msgstr "我需要为 Sleepycat 的 CacheLoader 付费吗？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2058
@@ -2371,12 +2386,14 @@
"from Sleepycat. See details at <ulink url=\"http://www.sleepycat.com/"
"jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink> ."
msgstr ""
+"如果你只是把它用于私人目的则不需要。但如果你分发带有 BdbjeCacheLoader 的产品，你就得从 Sleepycat 购买商业许可证。详情请访问 <ulink url=\"http://www.sleepycat.com/"
+"jeforjbosscache\">http://www.sleepycat.com/jeforjbosscache </ulink>。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2071
#, no-c-format
msgid "Can I use more than one cache loader?"
-msgstr ""
+msgstr "我可以使用多个 cache loader 吗？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2075
@@ -2389,7 +2406,7 @@
"non-null element of data. When performing writes, all cache loaders are "
"written to (except if the ignoreModifications element has been set to true "
"for a specific cache loader."
-msgstr ""
+msgstr "到 JBossCache 1.3.0 为止，可以。使用新的 CacheLoaderConfiguration XML 元素（请参考用户手册），你现在可以描述多个 cache loader。这样缓存就会按照配置顺序查找所有的 cache loader，直到它找到一个有效的、非空的数据元素。当执行写操作时，所有的 cache loader 都可以写入（除非某个 cache loader 的 ignoreModifications 元素已经设置为 true）。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2089
@@ -2398,7 +2415,7 @@
"Why do cache loaders go into an inconsistent state when I use transactions, "
"pessimistic locking, and I attempt to read a node after removing it from "
"within the same transaction scope?"
-msgstr ""
+msgstr "当我使用事务和悲观锁，且从相同的事务作用域里删除节点后试图读取它时，为什么 Cache loader 会进入不一致的状态？"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2096
@@ -2410,6 +2427,9 @@
"JBoss Cache 1.4.0. A very simple workaround if you're using JBoss Cache 1.3."
"x is to use optimistic locking."
msgstr ""
+"这是一个已知的程序错误（请参考 <ulink url=\"http://jira.jboss.com/jira/browse/"
+"JBCACHE-477\">JBCACHE-477</ulink> 和 <ulink url=\"http://jira.jboss.com/"
+"jira/browse/JBCACHE-352\">JBCACHE-352</ulink>），JBoss Cache 1.4.0 已经解决了这个问题。如果你在使用 JBoss Cache 1.3.x，使用乐观锁就是一个简单的绕过它的办法。"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:2104
@@ -2420,7 +2440,7 @@
"and remove someelements of that List within a transaction (when using "
"pessimistic locking and a cache loader), you may see IllegalStateExceptions "
"thrown."
-msgstr ""
+msgstr "这个程序错误的其中一个后果是：如果你使用的 PojoCache 带有对 List 的私有引用的 pojo，而且你在一个事务里（使用悲观锁和 cache loader）更新和删除了这个 List 的某些元素，那么你可以会遇到 IllegalStateExceptions。"
#. Tag: title
#: Cache_Frequently_Asked_Questions.xml:2116
More information about the jboss-cvs-commits
mailing list