9 Aug
2006
9 Aug
'06
9:33 a.m.
Johannes Winkelmann wrote: Hi,
Note: to avoid stressing the server we may want to generate static timelines (once a month?) in the future. Or as a simpler solution, we could just cache the svn log messages, such that only new ones are fetched from svn; a small sqlite db storing the already parsed commits, and the revision number up to where we fetched the messages should do the trick.
I like the idea of caching things into a sqlite db; for simplicity I'll work on caching the events from all sources so the visualization code in the wiki should come up cleaner, while we can do dirty stuff in the caching script.
P.S. Is there an RSS interface to that? ;-)
Sure, that'll be in version 2.0; we're at 0.0.1 right now ;-) Regards, Simone