future of HgKit

[marco gaddoni]

>
>  Also, a couple of people (including me) have suggested that what you
>  need is Mercurial in a "slave daemon" mode.  I.e. your Java
>  application (say an IDE) just starts an hg daemon and controls it via
>  a socket.  That cuts out much of the performance impact of repeatedly
>  spawning 'hg' subprocesses.
>

if a daemon mode is developed for mercurial,
running it under jython becomes a valid
alternative.
the jython performace problems come from
the startup of the interpreter.
and with jython you can commmit too.
-- 
"Reality continues to ruin my life." - Calvin.