On Mon, Feb 1, 2016 at 9:31 AM, Kjetil Matheussen <k.s.matheussen@gmail.com> wrote:


On Mon, Feb 1, 2016 at 3:02 PM, Paul Davis <paul@linuxaudiosystems.com> wrote:
 
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.

I was thinking of a new configuration protocol where any libjack client can function as server.

This already exists. I am a little shocked that you don't know this.
 
 
But it illustrates how flaky the system is when a bug like this can exist for 10 years.

No, it does not. It illustrates how shallow and low energy the development "team" for JACK is, especially on Windows.