No I don’t think it was that one, that looks significantly different than what I think I remember seeing (though it’s been near-on a decade now)…
In the blog posts related to the archive.org link you shared, the author is referencing following repo: Vagabond/egitd (which is a fork of the repo I posted lastly).
But yes, implementing it internally to allow for maximum concurrency is definitely the way to go.
I did not really implement it because of concurrency, but to have full control over the process and the possibility to add new features (hooks, fine grained permissions, etc.) in future.
EDIT: Make sure to benchmark the speed.
This is definitely on my list.
