[jboss-cvs] JBossAS SVN: r77182 - projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Aug 19 02:14:50 EDT 2008
Author: ldelima at redhat.com
Date: 2008-08-19 02:14:50 -0400 (Tue, 19 Aug 2008)
New Revision: 77182
Modified:
projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR/Cache_Frequently_Asked_Questions.po
Log:
translation ongoing
Modified: projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR/Cache_Frequently_Asked_Questions.po
===================================================================
--- projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR/Cache_Frequently_Asked_Questions.po 2008-08-19 04:04:48 UTC (rev 77181)
+++ projects/docs/enterprise/4.3/Cache/Cache_FAQ/pt-BR/Cache_Frequently_Asked_Questions.po 2008-08-19 06:14:50 UTC (rev 77182)
@@ -5,7 +5,7 @@
"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-19 14:04+1000\n"
+"PO-Revision-Date: 2008-08-19 16:14+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"
@@ -742,13 +742,15 @@
"for testing purposes only. But note that <literal>DummyTransactionManager</"
"literal> is not thread safe .i.e., it does not support concurrent "
"transactions. Instead, only one transaction is allowed at a time."
-msgstr "O JBoss Cache suporta qualquer TransactionManager que é compatível"
+msgstr ""
+"O JBoss Cache suporta qualquer TransactionManager que é compatível com o JTA, assim como o JBossTM. Um usuário pode configurar o gerenciador da transação através da definiçao xml de configuração. O JBossCache também um gerenciador de transação fictício interno (<literal>org.jboss.cache.tm.DummyTransactionManager</literal>), para fins de teste apenas. Mas, perceba que o <literal>DummyTransactionManager</"
+"literal> não é um segmento seguro, por exemplo: isto não suporta transações atuais. Ao invés disso, apenas uma transação é permitida de cada vez."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:633
#, no-c-format
msgid "How do I set up the cache to be transactional?"
-msgstr ""
+msgstr "Como é que eu posso configurar o cache para ser transacional?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:637
@@ -763,13 +765,13 @@
"trivial to implement this class to support other TransactionManagers. Once "
"this attribute is specified, the cache will look up the transaction context "
"from this transaction manager."
-msgstr ""
+msgstr "Você tanto usará o padrão (JBoss) TransactionManager para a execução do JBossCache dentro do JBoss, ou você tera'qie implementar a interface <literal>TransactionManagerLookup</literal> e retornar a uma instância de seu javax.transaction.TransactionManager. A propriedade de configuração <literal>TransactionManagerLookupClass</literal> define a classe a ser usada pelo cache para busca de uma referência a um TransactionManager. "
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:652
#, no-c-format
msgid "For the client code, here is a snippet to start and commit a transaction:"
-msgstr ""
+msgstr "Para o código do cliente, segue abaixo o trecho para inicializar e confirmar a transação:"
#. Tag: programlisting
#: Cache_Frequently_Asked_Questions.xml:656
@@ -797,7 +799,7 @@
#: Cache_Frequently_Asked_Questions.xml:662
#, no-c-format
msgid "How do I control the cache locking level?"
-msgstr ""
+msgstr "Como eu posso controlar o nível de bloqueamente do cache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:666
@@ -814,12 +816,15 @@
"ignored if optimistic locking is used. For details, please refer to the user "
"manual."
msgstr ""
+"O JBossCache permite você controlar o nível de bloqueamento do cache através do nível de isolação de transação. Isto é configurado através do atributo <literal>IsolationLevel</literal> . Atualmente, O JBossCache emprega um bloqueamento pessimista internamente. O Nível de isolação de transação a partir do bloqueamento pessimista corresponde aos níveis de isolações JDBC, nomeadamente <literal>NONE</literal>, <literal>READ_UNCOMMITTED</literal>, "
+"<literal>READ_COMMITTED</literal>, <literal>REPEATABLE_READ</literal> e "
+"<literal>SERIALIZABLE</literal>. Perceba que estes níveis de isolação são ignorados, caso o bloqueamento otimista for utilizado. Para maiores detalhes, por favor refira-se ao manual do usuário."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:693
#, no-c-format
msgid "How does JBoss Cache lock data for concurrent access?"
-msgstr ""
+msgstr "Como o JBoss Cache bloqueia os dados para o acesso atual?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:697
@@ -830,13 +835,13 @@
"optimistic locking to allow for greater concurrency at the cost of slight "
"processing overhead and performance. See the documentation for a more "
"detailed discussion on concurrency and locking in JBoss Cache."
-msgstr ""
+msgstr "Pelo padrão o JBoss Cache usa o bloqueamento pessimista para bloquear os nós dos dados, basenando-se no nível configurado de isolação. Desde o JBoss Cache 1.3.0, nós também oferecemos o bloqueamento otimista para permitir uma boa atualização de custo do pequeno processamento adia"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:709
#, no-c-format
msgid "How do I enable Optimistic Locking in JBoss Cache?"
-msgstr ""
+msgstr "Como eu ativo o Bloqueamento Otimista no JBoss Cache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:713
@@ -847,12 +852,16 @@
"set to <code>OPTIMISTIC</code> . Also note that <code>NodeLockingScheme</"
"code> defaults to <code>PESSIMISTIC</code> if omitted."
msgstr ""
+"Use the XMl attribute <code>NodeLockingScheme</code> . Note that "
+"<code>IsolationLevel</code> is ignored if <code>NodeLockingScheme</code> is "
+"set to <code>OPTIMISTIC</code> . Also note that <code>NodeLockingScheme</"
+"code> defaults to <code>PESSIMISTIC</code> if omitted."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:733
#, no-c-format
msgid "How does the write lock apply to an Fqn node, say, \"/org/jboss/test\"?"
-msgstr ""
+msgstr "How does the write lock apply to an Fqn node, say, \"/org/jboss/test\"?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:739
@@ -863,6 +872,10 @@
"\" (since the default separator is \"/\" for the fqn). The locking then is "
"applied to the node under root, for example \"/org\" (no locking \"/\")."
msgstr ""
+"First of all, JBossCache has a notion of <literal>root</literal> that serves "
+"as a starting point for every navigational operation. The default is \"/"
+"\" (since the default separator is \"/\" for the fqn). The locking then is "
+"applied to the node under root, for example \"/org\" (no locking \"/\")."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:747
@@ -873,12 +886,16 @@
"nodes recursively (in this example, \"/org\", and \"/org/jboss\"). Only when "
"it succeeds then it will try to obtain a write lock on \"/org/jboss/test\"."
msgstr ""
+"Furthermore, let's say when JBossCache needs to apply a write lock on node "
+"\"/org/jboss/test\", it will first try to obtain read lock from the parent "
+"nodes recursively (in this example, \"/org\", and \"/org/jboss\"). Only when "
+"it succeeds then it will try to obtain a write lock on \"/org/jboss/test\"."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:758
#, no-c-format
msgid "Can I use the cache locking level even without a transaction context?"
-msgstr ""
+msgstr "Can I use the cache locking level even without a transaction context?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:764
@@ -890,6 +907,11 @@
"node locking behavior outside of a transaction as if it is under transaction "
"with <literal>auto_commit</literal> on."
msgstr ""
+"Yes. JBossCache controls the individual node locking behavior through the "
+"isolation level semantics. This means even if you don't use a transaction, "
+"you can specify the lock level via isolation level. You can think of the "
+"node locking behavior outside of a transaction as if it is under transaction "
+"with <literal>auto_commit</literal> on."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:777
@@ -899,6 +921,9 @@
"INVALIDATION_ASYNC), how often does the cache broadcast messages over the "
"network?"
msgstr ""
+"With replication (REPL_SYNC/REPL_ASYNC) or invalidation (INVALIDATION_SYNC/"
+"INVALIDATION_ASYNC), how often does the cache broadcast messages over the "
+"network?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:783
@@ -911,12 +936,18 @@
"replication. Note that this has performance implication if network transport "
"is heavy (it usually is)."
msgstr ""
+"If the updates are under transaction, then the broadcasts happen only when "
+"the transaction is about to commit (actually during the prepare stage "
+"internally). That is, it will be a batch update. However, if the operations "
+"are not under transaction context, then each update will trigger "
+"replication. Note that this has performance implication if network transport "
+"is heavy (it usually is)."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:796
#, no-c-format
msgid "How can I do a mass removal?"
-msgstr ""
+msgstr "How can I do a mass removal?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:800
@@ -925,12 +956,14 @@
"If you do a cache.remove(\"/root\"), it will recursively remove all the "
"entries under \"/root\"."
msgstr ""
+"If you do a cache.remove(\"/root\"), it will recursively remove all the "
+"entries under \"/root\"."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:808
#, no-c-format
msgid "Can I monitor and manage the JBoss Cache?"
-msgstr ""
+msgstr "Can I monitor and manage the JBoss Cache?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:812
@@ -941,12 +974,16 @@
"chapter titled <emphasis role=\"bold\">Management Information</emphasis> in "
"the JBoss Cache user guide for more details."
msgstr ""
+"With JBoss Cache 1.3.0, you can if you are running JBoss Cache within JBoss "
+"AS or are using JDK 5.0's <literal>jconsole</literal> utility. See the "
+"chapter titled <emphasis role=\"bold\">Management Information</emphasis> in "
+"the JBoss Cache user guide for more details."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:824
#, no-c-format
msgid "Can I disable JBoss Cache management attributes in JBoss Cache 1.3.0?"
-msgstr ""
+msgstr "Can I disable JBoss Cache management attributes in JBoss Cache 1.3.0?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:828
@@ -957,6 +994,10 @@
"literal> ). See the chapter titled <emphasis role=\"bold\">Management "
"Information</emphasis> in the JBoss Cache user guide for more details."
msgstr ""
+"Yes, you can. Set the <literal>UseInterceptorMbeans</literal> configuration "
+"attribute to <literal>false</literal> (this defaults to <literal>true</"
+"literal> ). See the chapter titled <emphasis role=\"bold\">Management "
+"Information</emphasis> in the JBoss Cache user guide for more details."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:843
@@ -965,6 +1006,8 @@
"What is jboss-serialization.jar, introduced in JBoss Cache 1.4.x and do I "
"need this?"
msgstr ""
+"What is jboss-serialization.jar, introduced in JBoss Cache 1.4.x and do I "
+"need this?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:846
@@ -977,6 +1020,12 @@
"Java serialization. This very significantly improves replication performance "
"of custom objects placed in the cache."
msgstr ""
+"jboss-serialization.jar is the <ulink url=\"http://labs.jboss.org/portal/"
+"index.html?ctrl:id=page.default.info&project=serialization\"> JBoss "
+"Serialization </ulink> library, which is much more efficient in terms of "
+"speed and CPU usage as well as the generated byte stream size than standard "
+"Java serialization. This very significantly improves replication performance "
+"of custom objects placed in the cache."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:856
@@ -985,6 +1034,8 @@
"From 1.4.x, JBoss Cache relies on this library and it is needed to run JBoss "
"Cache."
msgstr ""
+"From 1.4.x, JBoss Cache relies on this library and it is needed to run JBoss "
+"Cache."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:864
@@ -993,6 +1044,8 @@
"Can I disable JBoss Serialization and revert back to standard Java "
"serialization?"
msgstr ""
+"Can I disable JBoss Serialization and revert back to standard Java "
+"serialization?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:868
@@ -1001,12 +1054,14 @@
"Yes you can, by passing in the <literal>-Dserialization.jboss=false</"
"literal> environment variable to your JVM."
msgstr ""
+"Yes you can, by passing in the <literal>-Dserialization.jboss=false</"
+"literal> environment variable to your JVM."
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:878
#, no-c-format
msgid "Does JBoss Cache support partitioning?"
-msgstr ""
+msgstr "Does JBoss Cache support partitioning?"
#. Tag: para
#: Cache_Frequently_Asked_Questions.xml:882
More information about the jboss-cvs-commits
mailing list