[Jack-Devel] Client-Server models are just fine. Please?
Paul Davis
paul at linuxaudiosystems.com
Mon Feb 1 17:47:09 CET 2016
On Mon, Feb 1, 2016 at 11:41 AM, Kjetil Matheussen <k.s.matheussen at gmail.com
> wrote:
>
>
>
> I'm suggesting to add gui functions which are calling an external program
> to configure jack, where the communication between libjack and the gui
> happens by sockets, not by stdout+stdin.
>
this already exists. your issue with it is the communication is currently
asymmetric: there is a structured protocol to configure and start the
server, but not in the reverse direction. you want errors and status
returned as well. and you want a structured protocol for this direction,
rather than semi-random line-oriented text.
> This will not make libjack
> link with a graphics library, and it will most likely not increase the
> size of libjack, and it will not make jackd disappear.
>
so how will an abritrary client become "the server" ?
it is just amazing to me, given all the other useful things that JACK could
be made to do, that anyone is talking about the mechanics of starting it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.linuxaudio.org/archives/jackaudio/attachments/20160201/75121fbe/attachment.html>
More information about the Jackaudio
mailing list