Does chg cache information?

[Yuya Nishihara]

On Sat, 19 Jan 2019 20:13:09 +0100, Marcus Harnisch wrote:
> What do you mean by “chg daemon process is forked per connection”? Isn't it
> that invoking chg (client) checks for a daemon, starting it when necessary?
> Subsequent invokation of chg would detect an already running daemon. What
> constitutes a connection here? When I work in two different repositories on
> the same machine, the same chg daemon is going to used, no?

Basically the same daemon waits new connection from chg (client), and the
daemon fork()s immediately after accept(). Then, a repository is loaded.

The long-lived daemon process is just handling new connections from chg
clients. No repository data would be loaded by it.