summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-09-28 00:17:34 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-09-28 00:17:34 +0000
commitc19da7ef086cd49eeeacbdfa7016e2e81207cbb0 (patch)
treee72564c5e0af8457fc5f3db9e8e50821b85953b6
parenta497ed2db38eedfc73f4b8f2ee00d5a18ab51eda (diff)
web commit by EthanGlasserCamp: questions about RecentChanges
-rw-r--r--doc/index/discussion.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index dc7fb14a7..9d3fdf7b8 100644
--- a/doc/index/discussion.mdwn
+++ b/doc/index/discussion.mdwn
@@ -20,3 +20,11 @@ something, that I think is very valuable.
> I'll be happy to point you in the right directions.. --[[Joey]]
----
+
+Some questions about the RecentChanges function.
+
+* Why isn't it statically-genereated, but generated dynamically by CGI? It seems like it could be beneficial to have it rendered in the post-commit hook, just like everything else in the wiki.
+* Also, is it planned/desired that recent changes generate the same information in RSS feed format? This seems like it could be a useful way to keep track of the wiki as a whole.
+* Lastly, would it be possible to use the recent changes code with a pagespec? I understand this sort of infringes on territory covered by the inline plugin, but the inline plugin only puts a page in the RSS feed once, when it's created, and I imagine some people -- some deranged, obsessive-compulsive people like myself -- would like to know about the changes made to existing pages as well as newly-created pages.
+
+Thanks for your time. -- Ethan \ No newline at end of file