Re: [LAD] [Jack-Devel] more jack/qjackctl madness : some comments

PrevNext  Index
DateTue, 19 May 2009 09:28:17 +0200
From Fons Adriaensen <[hidden] at kokkinizita dot net>
ToNedko Arnaudov <[hidden] at arnaudov dot name>
CcLinux Audio Developers <[hidden] at lists dot linuxaudio dot org>, JACK Developers <[hidden] at jackaudio dot org>
In-Reply-ToNedko Arnaudov Re: [LAD] [Jack-Devel] more jack/qjackctl madness : some comments
Follow-UpNedko Arnaudov Re: [LAD] [Jack-Devel] more jack/qjackctl madness : some comments
On Tue, May 19, 2009 at 10:03:28AM +0300, Nedko Arnaudov wrote:

> Fons Adriaensen <[hidden]> writes:
> 
> > Well, the current implementation *does* intercept C API
> > calls in order to divert them to dbus, it's not just an
> > addition to the standard jackd. I never mentioned babies
> > being eaten.
> 
> As long as interface is same at C API level everything is fine. dbus
> cant and does not intercept any C API calls. The implementation of the
> jack_client_open(), only when compiled in dbus model, only when wants to
> start jack server, starts the jack server by *CALLING* libdbus
> function. That C level libdbus API call is then implemented by using the
> dbus IPC mechanism (sockets) and then gets into jackdbus process that
> executes the call. Nobody is intercepting jack.h API C level calls.

Nedko, you continue to contradict yourself.

What you write above confirms that the jack_client_open()
call is intercepted and its action modified. 

Ciao,

-- 
FA

Io lo dico sempre: l'Italia è troppo stretta e lunga.
PrevNext  Index

1242718666.27730_0.ltw:2,a <20090519072817.GA2951 at zita2 dot kokkinizita dot net>