response

diff --git a/doc/bugs/svn-commit-hanging.mdwn b/doc/bugs/svn-commit-hanging.mdwn
index 73cae72322dd19fc5f2dc0ab92f0fce6e1d97176..5905210b1065524d94521bcfd04a59e7a185374b 100644 (file)
--- a/doc/bugs/svn-commit-hanging.mdwn
+++ b/doc/bugs/svn-commit-hanging.mdwn
@@ -1 +1,3 @@
-When I'm committing a page via the Web, Ikiwiki hangs at the `svn commit` stage. I'm sure that this is a result of all my local modifications, so there's no need to consider this a bug per se, but I'd be interested in hearing whether anybody else has seen this. -- [[Ben]]
\ No newline at end of file
+When I'm committing a page via the Web, Ikiwiki hangs at the `svn commit` stage. I'm sure that this is a result of all my local modifications, so there's no need to consider this a bug per se, but I'd be interested in hearing whether anybody else has seen this. -- [[Ben]]
+
+What kinds of local modifications are those? --[[Joey]]

diff --git a/doc/subversion/discussion.mdwn b/doc/subversion/discussion.mdwn
index f795e377413d5f03369bded6f7591cefbd002313..426735182cac57517c775d686c42eb951151b128 100644 (file)
--- a/doc/subversion/discussion.mdwn
+++ b/doc/subversion/discussion.mdwn
@@ -1 +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]]
\ No newline at end of file
+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]]