aboutsummaryrefslogtreecommitdiff
path: root/doc/rcs/svn
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-08-21 04:25:03 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-08-21 04:25:03 +0000
commit74baaeba00c90cd7a027e40e2f6d65695341a0e1 (patch)
tree6439c954ca575ce40bb965745d4cb67bec8f329e /doc/rcs/svn
parent764d91b6befacfca98676519b90a0c257d17f177 (diff)
downloadikiwiki-74baaeba00c90cd7a027e40e2f6d65695341a0e1.tar
ikiwiki-74baaeba00c90cd7a027e40e2f6d65695341a0e1.tar.gz
reorg all the pages about rcs backends. Fix all links
Diffstat (limited to 'doc/rcs/svn')
-rw-r--r--doc/rcs/svn/discussion.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/rcs/svn/discussion.mdwn b/doc/rcs/svn/discussion.mdwn
new file mode 100644
index 000000000..426735182
--- /dev/null
+++ b/doc/rcs/svn/discussion.mdwn
@@ -0,0 +1,13 @@
+If the user interrupts the page loading during the running of `svn commit`,
+the repository will be left in an inconsistent state. The probability of
+this happening increases with the size of the repository and the number of
+plugins installed, because these both affect how long the post-commit hook
+takes to run. (The core issue, I guess, is that we're abusing the concept
+of a "working copy" by giving everybody the same one). Here are the main
+solutions that I can see: (1) CGI queues commits so that a single process
+can act upon them sequentially, or (2) optionally divorce the `ikiwiki
+--refresh` from the `svn commit` so that commits happen faster. -- [[Ben]]
+
+I'm not aware of web servers, at least apache, killing cgi processes when
+the user stops a page load. If this is happening ikiwiki should be able to
+avoid it by blocking whatever signal is causing it to terminate. --[[Joey]]