1 Feb
2016
1 Feb
'16
7:31 a.m.
On Mon, Feb 1, 2016 at 3:02 PM, Paul Davis <paul(a)linuxaudiosystems.com>
wrote:
I was thinking of a new configuration protocol where any libjack client can
function as server.
But it illustrates how flaky the system is when a bug like this can exist
for 10 years.
2. It feels like a server configuration protocol
will stabilize faster if
clients also can function as servers
since more code is using it, not just qjackctl.
the server configuration protocol has existed for nearly 8 years. almost
nobody has chosen to use it, for anything at all. jackdbus is more or less
its only use case.
It works, but the more components you glue together, the higher the
chance is for something
to fail. For instance didn't the messages window in the windows version
of qjackctl show anything
coming from jackd until autumn 2015.
that has to do with windows and qjackctl, not with jackd.