On 08/04/2011 04:16 PM, Greg Stein wrote: > Finally, note that our intent is to switch to requesting content by > <path, SHA1> tuples in the future. Those will be *very* cacheable (the > SHA1 acts as the created-rev). So even if ra_serf didn't have the > happy accident of using the server-provided URL, we would be returning > to a cacheable form in 1.8.
Strictly speaking, in order to adhere to our current authz subsystem APIs (which require both an svn_fs_root_t and a path), we'd need to use <path, revision, SHA1>. mod_authz_svn doesn't take the root into consideration, but that's only one implementation of authz for Subversion. :-( -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
