[jboss-cvs] JBossAS SVN: r84033 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Feb 10 01:36:47 EST 2009
Author: xhuang at jboss.com
Date: 2009-02-10 01:36:47 -0500 (Tue, 10 Feb 2009)
New Revision: 84033
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po 2009-02-10 06:29:54 UTC (rev 84032)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JBoss_Cache_JGroups.po 2009-02-10 06:36:47 UTC (rev 84033)
@@ -9,8 +9,8 @@
"Project-Id-Version: Clustering_Guide_JBoss_Cache_JGroups\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-02-09 17:14+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2009-02-10 15:33+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -2171,7 +2171,7 @@
"application that makes synchronous group RPC calls. If a channel is only "
"used for a cache configured for REPL_SYNC, we recommend you remove FC from "
"its protocol stack."
-msgstr ""
+msgstr "配置为 REPL_SYNC 的 JBoss Cache 群集是进行同步组 RPC 调用的应用程序的一个范例。如果某个频道只用于配置为 REPL_SYNC 的缓存，我们推荐你从其协议栈里删除 FC。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:789
@@ -2181,7 +2181,7 @@
"a TCP-based protocol stack is unnecessary. There is no group beyond the "
"single peer-to-peer relationship, and TCP's internal flow control will "
"handle that just fine."
-msgstr ""
+msgstr "当然，如果你的群集只由两个节点组成，在基于 TCP 的协议栈包含 FC 是不必要的。组不会超越单个点对点的关系，使用 TCP 的内部流量控制就可以了。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:792
@@ -2195,12 +2195,14 @@
"engineered buddy replication use case these should be infrequent. But if you "
"remove FC be sure to load test your application.)"
msgstr ""
+"不需要 FC 的另外一个情况是配置了 buddy 复制且为单一 buddy 的 JBoss "
+"Cache 所使用的频道。这样的频道在许多方面就象一个两节点的群集，消息只在两者之间（亦即 buddy）交换。和数据 gravitation 相关的其他消息也有可能发往所有节点，但在正确设置的 Buddy 复制情景下，这应该是不频繁的。如果你删除了 FC，请确保加载并测试你的应用程序。）"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:802
#, no-c-format
msgid "Fragmentation"
-msgstr ""
+msgstr "Fragmentation"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:803
@@ -2210,7 +2212,7 @@
"the receiver's side. It works for both unicast and multicast messages. It is "
"configured in the FRAG2 sub-element under the JGroups Config element. Here "
"is an example configuration."
-msgstr ""
+msgstr "这个协议将超过设定大小的消息分段，并在接收者端进行重组。它可用于单播和多播消息。它在 JGroups 的 Config 元素下的 FRAG2 子元素里进行配置。下面是一个配置示例。"
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:806
@@ -2220,22 +2222,23 @@
" <FRAG2 frag_size=\"60000\" down_thread=\"false\" up_thread="
"\"false\"/>]]>"
msgstr ""
+"<![CDATA[ \n"
+" <FRAG2 frag_size=\"60000\" down_thread=\"false\" up_thread="
+"\"false\"/>]]>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:808
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The configurable attributes in the FRAG2 element are as follows."
-msgstr "下列是 <literal>FC</literal> 元素的可配置属性。"
+msgstr "FRAG2 元素里的可配置属性如下："
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:813
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">frag_size</emphasis> specifies the max frag size in "
"bytes. Messages larger than that are fragmented."
-msgstr ""
-"<emphasis role=\"bold\">max_credits</emphasis> 指定最大的信用值（字节数）。这"
-"个值应该小于 JVM 的 heap size。"
+msgstr "<emphasis role=\"bold\">frag_size</emphasis> 指定最大的分段大小（字节数）。大于这个值的消息将被分段。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:817
@@ -2245,7 +2248,7 @@
"protocol is still needed if FC is used. The reason for this is that if you "
"send a message larger than FC.max_bytes, FC protocol would block. So, "
"frag_size within FRAG2 needs to be set to always be less than FC.max_bytes."
-msgstr ""
+msgstr "TCP 协议已经提供了分段功能但如果使用 FC，你仍然需要 JGroups 的分段协议。其原因是如果你发送了一个大于 FC.max_bytes 的消息，FC 协议将会阻塞。所以，FRAG2 里的 frag_size 总是需要设置为比 FC.max_bytes 小的值。"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:826
@@ -2270,12 +2273,9 @@
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:831
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<pbcast.STATE_TRANSFER down_thread=\"false\" up_thread=\"false\"/>"
-msgstr ""
-"<pbcast.STATE_TRANSFER \n"
-" down_thread=\"false\"\n"
-" up_thread=\"false\"/>"
+msgstr "<pbcast.STATE_TRANSFER down_thread=\"false\" up_thread=\"false\"/>"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:835
@@ -2305,7 +2305,7 @@
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:840
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<pbcast.STABLE stability_delay=\"1000\"\n"
" desired_avg_gossip=\"5000\" \n"
@@ -2314,8 +2314,8 @@
msgstr ""
"<pbcast.STABLE stability_delay=\"1000\"\n"
" desired_avg_gossip=\"5000\" \n"
-" down_thread=\"false\"\n"
-" max_bytes=\"250000\"/>"
+" down_thread=\"false\" up_thread=\"false\"\n"
+" max_bytes=\"400000\"/>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:842
@@ -2355,7 +2355,7 @@
"<emphasis role=\"bold\">stability_delay</emphasis> specifies delay before we "
"send STABILITY msg (give others a change to send first). If used together "
"with max_bytes, this attribute should be set to a small number."
-msgstr ""
+msgstr "<emphasis role=\"bold\">stability_delay</emphasis> 指定在发送 STABILITY 消息之前的延迟时间。如果和 max_bytes 一起使用，这个属性应该设置为比它更小的值。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:859
@@ -2389,14 +2389,15 @@
#. Tag: programlisting
#: Clustering_Guide_JBoss_Cache_JGroups.xml:869
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<MERGE2 max_interval=\"10000\"\n"
" min_interval=\"2000\"\n"
" down_thread=\"false\" up_thread=\"false\"/>"
msgstr ""
"<MERGE2 max_interval=\"10000\"\n"
-" min_interval=\"2000\"/>"
+" min_interval=\"2000\"\n"
+" down_thread=\"false\" up_thread=\"false\"/>"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:875
@@ -2440,13 +2441,13 @@
"even though shunning is disabled. Alternatively use MPING, which is commonly "
"used with TCP to provide multicast member discovery capabilities, instead of "
"TCPPING to avoid having to specify all the nodes."
-msgstr ""
+msgstr "群集状态不会在 Merger 里合并，这必须由应用程序来完成。如果 <literal>MERGE2</literal> 和 TCPPING 一起使用，为了使合并过程正常进行，<literal>initial_hosts</literal> 属性必须包含所有可能被合并的节点。否则，合并过程将不会合并所有的节点，即使是禁用了 shunning。如果我们使用 MPING（通常和 TCP 一起使用）而不是 TCPPING来提供多播成员发现能力，那就可以避免指定所有的节点。"
#. Tag: title
#: Clustering_Guide_JBoss_Cache_JGroups.xml:892
#, no-c-format
msgid "Binding JGroups Channels to a particular interface"
-msgstr ""
+msgstr "把 JGroups 频道绑定到特定的接口"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:893
@@ -2455,7 +2456,7 @@
"In the Transport Protocols section above, we briefly touched on how the "
"interface to which JGroups will bind sockets is configured. Let's get into "
"this topic in more depth:"
-msgstr ""
+msgstr "在上面的“传输协议”章节里，我们简短地介绍了如何配置 JGroups 把套接字绑定到哪个接口。让我们进一步深入讨论这个主题："
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:896
@@ -2468,7 +2469,7 @@
"property trumps XML. If JBoss AS is started with the -b (a.k.a. --host) "
"switch, the AS will set <literal>jgroups.bind_addr</literal> to the "
"specified value."
-msgstr ""
+msgstr "首先，理解这一点很重要：如果系统属性 jgroups.bind_addr（早期版本里称为 <literal>bind.address</literal>）已经被设置，在 XML 配置文件里的任何 bind_addr 元素里设置的值将被 JGroups 所忽略。系统属性优先于 XML 设置。如果 JBoss AS 启动时使用 -b（也就是 --hos）开关，AS 将设置 <literal>jgroups.bind_addr</literal> 为指定的值。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:899
@@ -2478,7 +2479,7 @@
"to localhost if -b is not set. The effect of this is that in most cases "
"users are going to be setting -b and thus jgroups.bind_addr is going to be "
"set and any XML setting will be ignored."
-msgstr ""
+msgstr "从 AS 4.2.0 开始，处于安全原因，如果没有设置 -b 选项，AS 将把大多数服务绑定到本地主机。因此在大多数情况下，用户会设置 -b，所以 jgroups.bind_addr 将被设置，相关 XML 配置将被忽略。"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:902
@@ -2486,7 +2487,7 @@
msgid ""
"So, what are <emphasis>best practices</emphasis> for managing how JGroups "
"binds to interfaces?"
-msgstr ""
+msgstr "所以，管理 JGroups 绑定到什么接口的<emphasis>最佳实践</emphasis>是什么？"
#. Tag: para
#: Clustering_Guide_JBoss_Cache_JGroups.xml:907
More information about the jboss-cvs-commits
mailing list