Re: request to make svn_wc__prop_list_recursive a public API

On 17.02.2011 14:19, Hyrum K Wright wrote:

> <aside>
> Last summer in Berlin we had a quite heated discussion about just
> deprecating all of libsvn_wc APIs. I was against such a move (at
> least until 2.0) in that it would leave the existing APIs public, but
> any new ones private, and the whole interface in limbo. I still feel
> that way, and this discussion vindicates that feeling (at least to me
> :) ).
> </aside>

Removing all the libsvn_wc APIs is a bad idea. For example, the new
status function returns a *lot* less information than the deprecated
ones. The only way to get that information back now without a *huge*
performance loss is to use those APIs in the status callback. Without
those, fetching the missing information requires accessing the disk over
and over again using different svn_client_ APIs.

So either you have to provide as much information as possible in e.g.
svn_client_status or not remove the libsvn_wc APIs. You can't do both
remove information and remove the APIs if you want to keep svn clients
useful and fast.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net