Re: [LAD] New proposal for the jackd/jackdbus mess

PrevNext  Index
DateMon, 25 May 2009 16:27:28 -0700
From Fernando Lopez-Lezcano <[hidden] at ccrma dot Stanford dot EDU>
ToKrzysztof Foltman <[hidden] at foltman dot com>
CcJack devel <[hidden] at lists dot jackaudio dot org>, Linux Audio Developers <[hidden] at lists dot linuxaudio dot org>
In-Reply-ToKrzysztof Foltman Re: [LAD] New proposal for the jackd/jackdbus mess
Follow-UpPaul Davis Re: [LAD] [Jack-Devel] New proposal for the jackd/jackdbus mess 
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
PrevNext  Index

1243294031.20386_0.ltw:2,a <1243294048.29995.42.camel at localhost dot localdomain>