On Sat, Mar 17, 2007, Eduard Bloch wrote: > Ok, forget it. I was convinced to stop caching the detected values. > Let's see whether people would like this behavior more.
Yes, a cache is only an useful addition if you can easily tell whether it's up-to-date. But at least I now understand that this was meant as a cache, not a configuration, and mostly because of login roundtrips and SSH passwords. I think you can address the same speed + number of logins problems by using the SVN bindings instead of invoking the command-line client. From a quick look at the API, SVN::Ra seems to offer primitives to connect and do some remote operations without reopening the connection; but SVN::Client also seems to be enough for the uses of sbp. I checked whether refactoring of the current "svn" invocations could fix this: you basically do foreach url (@candidates) insvn($url), and each insvn() does a "svn ls" but you can call "svn ls" with multiple arguments. But this didn't help, "svn" opens a connection per parameter, even if these are in the same repo. -- Loïc Minier
