Bert Huijben wrote: > Most simple clients can just use svn_client_status5() and trust the results > to be complete like they were used to, but more advanced clients can use > svn_wc_walk_status() to get higher performance. > > E.g. If TortoiseSVN or AnkhSVN switched to the wc apis, they can just show > the conflicted glyph when it sees the conflict on a 2 GB file, instead of > also comparing that file against its base version. And if you run status > just to show a glyph for a modification on a subdirectory it is not > necessary to perform comparation on the rest of the files, when you found a > single change. (But you would want the conflict results)
I really, really don't like the idea of encouraging the continued use of WC APIs by third-party consumers. We should begin *right now* discouraging its use and simply improving the svn_client API to better serve our various clients. (I thought we had, in general, consensed around this plan already, but I guess I was wrong.) -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
