[svnbook] r6012 committed - branches/1.8/zh/book
wuzhouhui at users.sourceforge.net
wuzhouhui at users.sourceforge.net
Mon Nov 18 14:42:43 UTC 2019
Revision: 6012
http://sourceforge.net/p/svnbook/source/6012
Author: wuzhouhui
Date: 2019-11-18 14:42:42 +0000 (Mon, 18 Nov 2019)
Log Message:
-----------
1.8/zh: resolve some TODO
Modified Paths:
--------------
branches/1.8/zh/book/appd-berkeley-db.xml
branches/1.8/zh/book/ch08-embedding-svn.xml
Modified: branches/1.8/zh/book/appd-berkeley-db.xml
===================================================================
--- branches/1.8/zh/book/appd-berkeley-db.xml 2019-11-12 11:34:17 UTC (rev 6011)
+++ branches/1.8/zh/book/appd-berkeley-db.xml 2019-11-18 14:42:42 UTC (rev 6012)
@@ -195,7 +195,6 @@
<emphasis>not</emphasis> actually meet those requirements.
And in no case can you allow a BDB-backed repository that
resides on a network share to be accessed by multiple
- ### TODO
clients of that share at once (which quite often is the
whole point of having the repository live on a network share
in the first place).</para>
@@ -204,9 +203,9 @@
<footnote><para>Berkeley DB 要求底层的文件系统实现了严格的 POSIX
锁语义, 更重要的是还要支持将文件直接映射到进程的内存中.
</para></footnote>, 它可以正常工作, 但大部分网络文件系统和应用程序
- 其实并 <emphasis>不满足</emphasis> 这些规范. 另外, 管理员没办法让
- 多个客户端同时访问位于网络共享目录内的, 基于 BDB 的 Subversion
- 仓库.</para>
+ 其实并 <emphasis>不满足</emphasis> 这些规范. 另外, 位于网络共享目录
+ 内的, 基于 BDB 的 Subversion 不允许多个客户端同时访问 (而这却是把
+ 仓库放在共享目录后无法避免的问题).</para>
<warning>
<!--
Modified: branches/1.8/zh/book/ch08-embedding-svn.xml
===================================================================
--- branches/1.8/zh/book/ch08-embedding-svn.xml 2019-11-12 11:34:17 UTC (rev 6011)
+++ branches/1.8/zh/book/ch08-embedding-svn.xml 2019-11-18 14:42:42 UTC (rev 6012)
@@ -437,7 +437,6 @@
<para>The notion of a Subversion transaction can become easily
confused with the transaction support provided by the
underlying database itself, especially given the former's
- ### TODO
close proximity to the Berkeley DB database code in
<filename>libsvn_fs_base</filename>. Both types of
transaction exist to provide atomicity and isolation. In
@@ -448,7 +447,9 @@
happened—and in a way that does not interfere with
other processes acting on the data.</para>
-->
- <para>用户很容易把 Subversion 的事务与后端数据库所提供的事务支持弄混.
+ <para>用户很容易把 Subversion 的事务与后端数据库所提供的事务支持弄混,
+ 特别是考虑到前者在 <filename>libsvn_fs_base</filename> 里的代码和
+ Berkeley DB 数据库的代码非常接近.
这两种事务都用于提供原子性和隔离性, 换句话说, 事务允许用户以这样一
种方式执行一个操作集合—要么集合中的所有操作都执行成功, 要么一
个都不执行—同时不会干扰到操作数据的其他进程.</para>
@@ -2011,7 +2012,6 @@
interesting uses for the Subversion API, from simple repository
hook scripts, to integrations between Subversion and some other
application, to completely different version control systems.
- ### TODO
What unique itch will <emphasis>you</emphasis> scratch with
it?</para>
-->
More information about the svnbook-dev
mailing list