25 May
2009
25 May
'09
9:26 p.m.
On Wed, 2009-05-20 at 11:20 +0100, Krzysztof Foltman wrote:
Stéphane Letz wrote:
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
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 ;)