Daniel Shahaf <danie...@elego.de> writes: > I believe you cannot assume svn_fs_t's will be short lived, and > _certainly_ cannot assume that the access pattern to an svn_fs_t > will be in any way related to random clients having random RA > sessions; for all the FS API knows, svnserve is a daemon that calls > svn_fs_open() once per reboot. > > And yes, people do this.
Perhaps the read routines could be changed to always read the revprop-gen file and refresh the cache if required. Obviously this would involve more IO than the current caching strategy, but it would still be more efficient than the the previous non-cached approach. -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
