Hi all, I think I've come up with a better way to manage the vc cache.
As you know, we currently only store the information directly needed for the TracChangeset component. The TracBrowser part still needs to have direct access to the repository and make use of the cache. The proposed change would make it possible to implement the `get_node()/get_entries()` methods in a generic an efficient way. More details here: http://projects.edgewall.com/trac/wiki/VcRefactoring#SupportforBigRepositories I have the feeling that this cached information can be used for other needs as well: * next/prev revision for a given path * implement efficiently the revision graph view (#1445) Also, I'd like to get some feedback about the possible choices we have for handling multiple repositories: http://projects.edgewall.com/trac/wiki/VcRefactoring#SupportforMultipleRepositories Thanks for your time, -- Christian _______________________________________________ Trac-dev mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac-dev
