On Wed, 2009-05-20 at 11:20 +0100, Krzysztof Foltman wrote:
> Stéphane Letz wrote:
>
> > This scheme seems to hopefully solve most of the problems we had, and
> > requires only a bit of change for the "jackdbus" front-end to continue
> > working, but not much.
>
> One obvious problem is that it will be necessary to create yet another
> IPC protocol for control communication between libjack.so and
> libjackserver.so. Why not use something already proven and with existing
> tools like call monitor, command line interface etc. - that's why D-Bus
> was used in first place.
>
> Don't we already have too much NIH?
>
> Oh well, maybe not ;)
One problem is that it is not necessarily true that dbus will always be
running when you want to run jack. Tying basic stuff like running jack
to an external server (dbus is a server) does not look to me like a good
idea.
-- Fernando
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Tue May 26 04:15:04 2009
This archive was generated by hypermail 2.1.8 : Tue May 26 2009 - 04:15:04 EEST