Re: [Jack-Devel] Client-Server models are just fine. Please?

PrevNext  Index
DateMon, 01 Feb 2016 15:31:22 +0100
From Kjetil Matheussen <[hidden] at gmail dot com>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
Cc"[hidden] at lists dot jackaudio dot org" <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] Client-Server models are just fine. Please?
Follow-UpDavid Nielson Re: [Jack-Devel] Client-Server models are just fine. Please?
Follow-Upsqweek Re: [Jack-Devel] Client-Server models are just fine. Please?
Follow-UpPaul Davis Re: [Jack-Devel] Client-Server models are just fine. Please?
On Mon, Feb 1, 2016 at 3:02 PM, Paul Davis <[hidden]>
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.



>
>
>>
>>
>> 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.
>
>
But it illustrates how flaky the system is when a bug like this can exist
for 10 years.
PrevNext  Index

1454337088.18560_0.ltw:2, <CAC6niE+vjjZQGjpXD+EuKbq=a2ha_XsoPyoR2htTTt4SX4T_xg at mail dot gmail dot com>