On Mon, May 18, 2009 at 10:24:45PM +0100, Chris Cannam wrote: > On Mon, May 18, 2009 at 3:25 PM, MarcO'Chapeau <marco@xxxxxxxxxxxxxxxx> wrote: > > The new feature in JACK2 is the control API. That is: a *C control API*. > > Now it is very important to read the previous sentence over and over again. > > Once the dbus keyword has disappeared of your focus, read on. > > > > So, this C/C++ control API allows one to start/stop jack, configure it, and > > manage connections in between clients. jackdbus [does] that > > through a DBUS interface. > > Thanks Marc, that was a really helpful summary. > > I wasn't quite sure whether to be outraged by or indifferent to this > whole argument; now I'm _reasonably_ sure I can write it down to > technical problems rather than a big conceptual worry, and go back to > sleep instead. > > So this kerfluffle is not related to clients but rather to packagers? The control interface is available *publicly* to other clients, but JACK uses dbus *internally* between its component parts, and thus no JACK app need use dbus if it doesn't want to? Seems reasonable to me. Another dependency, perhaps, but not a huge major big deal. -ken _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
