[jboss-cvs] JBossAS SVN: r78837 - projects/docs/enterprise/4.3/Cache/Cache_Tree_Cache_Guide/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Sep 25 00:12:08 EDT 2008
Author: ldelima at redhat.com
Date: 2008-09-25 00:12:08 -0400 (Thu, 25 Sep 2008)
New Revision: 78837
Modified:
projects/docs/enterprise/4.3/Cache/Cache_Tree_Cache_Guide/pt-BR/Replication.po
Log:
proofread in progress
Modified: projects/docs/enterprise/4.3/Cache/Cache_Tree_Cache_Guide/pt-BR/Replication.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_Tree_Cache_Guide/pt-BR/Replication.po 2008-09-25 03:58:48 UTC (rev 78836)
+++ projects/docs/enterprise/4.3/Cache/Cache_Tree_Cache_Guide/pt-BR/Replication.po 2008-09-25 04:12:08 UTC (rev 78837)
@@ -9,7 +9,7 @@
"Project-Id-Version: Replication\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-09-21 04:44+0000\n"
-"PO-Revision-Date: 2008-09-25 13:58+1000\n"
+"PO-Revision-Date: 2008-09-25 14:12+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -31,13 +31,13 @@
"(standalone) or clustered. If in a cluster, the cache can be configured to "
"replicate changes, or to invalidate changes. A detailed discussion on this "
"follows."
-msgstr ""
+msgstr "O <literal>TreeCache</literal> pode ser configurado para local (autônomo) ou com cluster. No caso de cluster, o cache pode ser configurado para replicar as alterações replicadas ou para invalidar as alterações. Você poderá encontrar mais informações referentes a este assunto em frente."
#. Tag: title
#: Replication.xml:10
#, no-c-format
msgid "Local Cache"
-msgstr ""
+msgstr "Cache Local"
#. Tag: para
#: Replication.xml:11
@@ -47,13 +47,13 @@
"a cluster. Therefore their elements don't need to be serializable - however, "
"we recommend making them serializable, enabling a user to change the cache "
"mode at any time."
-msgstr ""
+msgstr "Os caches locais não juntam-se a um cluster e não comunicam-se com os outros nós num cluster. Portanto, seus elementos não precisam ser serializáveis - no entanto recomendamos torná-los serializáveis, permitindo que um usuário altere o modo do cache a qualquer momento."
#. Tag: title
#: Replication.xml:17
#, no-c-format
msgid "Clustered Cache - Using Replication"
-msgstr ""
+msgstr "Cache com Cluster - Utilizando a Replicação"
#. Tag: para
#: Replication.xml:18
@@ -63,6 +63,8 @@
"literal> instances in the cluster. Replication can either happen after each "
"modification (no transactions), or at the end of a transaction (commit time)."
msgstr ""
+"Os caches replicados replicam todas as alterações a outras instâncias do <literal>TreeCache</"
+"literal> num cluster. A replicação pode tanto acontecer após cada modificação (sem transações) ou no final de uma transação (período de confirmação)."
#. Tag: para
#: Replication.xml:21
@@ -450,6 +452,65 @@
"</config>\n"
"</attribute>"
msgstr ""
+"<!-- Buddy Replication config -->\n"
+"<attribute name=\"BuddyReplicationConfig\">\n"
+"<config>\n"
+" \n"
+"<!-- Enables buddy replication. This is the ONLY mandatory configuration "
+"element here. -->\n"
+"<buddyReplicationEnabled>true</buddyReplicationEnabled>\n"
+" \n"
+"<!-- These are the default values anyway -->\n"
+"<buddyLocatorClass>\n"
+" org.jboss.cache.buddyreplication.NextMemberBuddyLocator\n"
+"</buddyLocatorClass>\n"
+" \n"
+"<!-- numBuddies is the number of backup nodes each node maintains. \n"
+"ignoreColocatedBuddies means that each node will *try* to select a buddy on "
+"a different \n"
+"physical host. If not able to do so though, it will fall back to colocated "
+"nodes. -->\n"
+"<buddyLocatorProperties>\n"
+" numBuddies = 1\n"
+" ignoreColocatedBuddies = true\n"
+"</buddyLocatorProperties>\n"
+" \n"
+"<!-- A way to specify a preferred replication group. If specified, we "
+"try to pick a \n"
+"buddy who shares the same pool name (falling back to other buddies if not "
+"available).\n"
+"This allows the sysdmin to hint at backup buddies are picked, so for "
+"example, nodes may be \n"
+"hinted to pick buddies on a different physical rack or power supply for "
+"added fault tolerance. \n"
+"-->\n"
+"<buddyPoolName>myBuddyPoolReplicationGroup</buddyPoolName>\n"
+" \n"
+"<!-- Communication timeout for inter-buddy group organisation messages "
+"(such as assigning \n"
+"to and removing from groups, defaults to 1000. -->\n"
+"<buddyCommunicationTimeout>2000</buddyCommunicationTimeout>\n"
+"\n"
+"<!-- Whether data is removed from old owners when gravitated to a new "
+"owner. \n"
+"Defaults to true. -->\n"
+"<dataGravitationRemoveOnFind>true</dataGravitationRemoveOnFind>\n"
+"\n"
+"<!-- Whether backup nodes can respond to data gravitation requests, or "
+"only the data owner \n"
+"is supposed to respond. Defaults to true. -->\n"
+"<dataGravitationSearchBackupTrees>true</"
+"dataGravitationSearchBackupTrees>\n"
+"\n"
+"<!-- Whether all cache misses result in a data gravitation request. "
+"Defaults to false, \n"
+"requiring callers to enable data gravitation on a per-invocation basis using "
+"the Options API. \n"
+"-->\n"
+"<autoDataGravitation>false</autoDataGravitation>\n"
+"\n"
+"</config>\n"
+"</attribute>"
#. Tag: title
#: Replication.xml:141
More information about the jboss-cvs-commits
mailing list