> doing this in such a way that would work well with multithreaded clients
> would require adding a context argument that gets passed down with each
> call and inserting calls to a user supplied callback that checks to see
> if it should back out in various places, or using a global
> callback/context and inserting the calling of the callback into the
> SVN_ERR macro (that's what mine did).
Yes, but since multithreaded clients must take care also that two
SubVersion tasks don't affect the same working copy (locked files)
it would not be too much to ask for such clients to also take care
of global callback/contexts.
I even wonder if multithreaded clients have some use...
> if people are OK with the global callback/context technique (which means
> that multithreaded clients are required to use thread specific storage
> inside their callback in order to support multiple cancelable svn
> actions in separate threads), i'd be happy to dig up the patches and
> make them work again, but i don't have the time or the energy to do it
> the other way.
I'd apreciate that!
SteveKing
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 17 19:08:19 2002