VCS Interface classes (async execution)

[Matthew Woehlke]

Andreas Pakulat wrote:
> On 02.05.07 11:14:59, Matthew Woehlke wrote:
>> Jakob Petsovits wrote:
>>> On Monday, 30. April 2007, Andreas Pakulat wrote:
>>>> I present to you our new VCS interface classes (that I finally managed
>>>> to write up, based on the enourmus thread some time ago).
>>> Other question: is it ok to let each VCS plugin reinvent threading?
>> Andreas brought up the idea of using KJob. Probably you will not 
>> reimplement threading, but use some standard job class.
> 
> Uhm, as dukju already found KJob doesn't to any threading or such
> things. You have to do that yourself, so this point is valid. However
> not all plugins may need a separate thread, for example cvs runs the
> client and parses its output (I guess) so we don't need a thread here.

Hmm, right... is ThreadWeaver good for this sort of thing? Anyway for 
cvs and perforce (both of which have no API and so must rely on spawning 
  the CLI client) this, as you point out, is not an issue. :-)

-- 
Matthew
"Doggy!" -- Robots from Freefall (http://freefall.purrsia.com)