On Thu, Feb 17, 2011 at 12:47:32PM +0100, Stefan Küng wrote: > Hi, > > The new function svn_wc__prop_list_recursive() provides a big > performance gain for listing all properties of a full working copy. > Currently I have to use svn_client_proplist3() to make use of that. > > But I'd like to have that API accessible directly, the same way e.g. > svn_wc_prop_list2(). It is much easier to use those APIs for > accessing the working copy because then I don't have to set up a > full client context. > > Of course if you like to keep that API private, I'm ok with that too > since I can use the svn_client_ API instead if I have to. > > Thoughts?
I would prefer not to expose the WC API directly. I think that was a mistake, because it complicated the wc-ng effort since it had to cater to consumers of these APIs. We should make sure that the libsvn_client API provides sufficient access to the WC layer without exposing implementation details. If setting up a client context is too much overhead, then maybe we should try to address that problem, instead of ignoring it and making all the WC APIs public again.
