[svnbook commit] r2615 - trunk/src/en/book

[cmpilato]

Author: cmpilato
Date: Fri Jan  5 09:49:36 2007
New Revision: 2615

Modified:
   trunk/src/en/book/ch-advanced-topics.xml

Log:
* src/en/book/ch-advanced-topics.xml
  Describe the problem with externals definitions and multiple RA layers.


Modified: trunk/src/en/book/ch-advanced-topics.xml
==============================================================================
--- trunk/src/en/book/ch-advanced-topics.xml	(original)
+++ trunk/src/en/book/ch-advanced-topics.xml	Fri Jan  5 09:49:36 2007
@@ -2489,9 +2489,23 @@
 $
 </screen>
 
-    <para>Be aware, too, that if you need to re-parent your working
-      copy (using <command>svn switch --relocate</command>), externals
-      definitions will <emphasis>not</emphasis> also be
+    <para>Also, the fact that externals definitions use absolute URLs
+      can cause problems with repositories that are available via
+      multiple URL schemes.  For example, if your Subversion server is
+      configured to allow everyone to checkout the repository over
+      <literal>http://</literal> or <literal>https://</literal>, but
+      only allow commits to come in via <literal>https://</literal>,
+      you have an interesting problem on your hands.  If your
+      externals definitions use the <literal>http://</literal> form
+      of the repository URLs, you won't be able to commit anything
+      from the working copies created by those externals.  On the
+      other hand, if they use the <literal>https://</literal> form of
+      the URLs, anyone who might be checking out via
+      <literal>http://</literal> because their client doesn't support
+      <literal>https://</literal> will be unable to fetch the external
+      items.  Be aware, too, that if you need to re-parent your
+      working copy (using <command>svn switch --relocate</command>),
+      externals definitions will <emphasis>not</emphasis> also be
       re-parented.</para>
 
     <para>Finally, there might be times when you would prefer that