[Tickets #2112] Re: CVS Activity Log/Monitor
bugs at horde.org
bugs at horde.org
Fri Feb 15 06:03:25 UTC 2008
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/?id=2112
-----------------------------------------------------------------------
Ticket | 2112
Updated By | Chuck Hagenbuch <chuck at horde.org>
Summary | CVS Activity Log/Monitor
Queue | Chora
Version | HEAD
Type | Enhancement
State | Accepted
Priority | 1. Low
Milestone |
Patch |
Owners |
-----------------------------------------------------------------------
Chuck Hagenbuch <chuck at horde.org> (2008-02-15 01:03) wrote:
Some ideas from Michael Naberezny via IRC log:
[16:39] <mnaberez> seems chora could just page cache, and all the commit
hook would need
to do is invalidate the cache
[16:41] <mnaberez> that doesn't help with the timeline, but that's
something that can
just be generated once with `svn log` and page cached, and then
invalidated by the hook.
reporting and storing all kinds of stats is hard
[16:43] <cjh> also harder for cvs
[16:44] <mnaberez> cjh: in what sense?
[16:45] <cjh> generating a timeline for the whole repository in CVS is a
royal pain
[16:49] <mnaberez> cjh: if the stats were generated per commit by the
repository hook,
features like timeline would only work from the time after the hook was
installed. it
seems you'd need to collect that back information from the repository
anyway.
[17:03] <cjh> right, but you could do it once and then update it
incrementally
[17:03] <cjh> instead of all at once when it was invalidated
[17:06] <mnaberez> cjh: this is why i suggested that it might invalidate a
page cache.
if the hook reported a file changed, you would invalidate the cached page
for that file's
directory, and invalidate the first page of the timeline. that's
straightforward, and
then the same mechanism is always used to generate those pages
[17:07] <cjh> ah
[17:13] <mnaberez> cjh: i think collecting statistics would be much more
interesting, but
also much harder. i guess it depends on what the goals are (make chora
faster vs more
features)
More information about the bugs
mailing list