So if I understand this correctly (and please correct me if I am wrong), we
now have a way to build jack clients which work only with dbus or with
direct access to C API? If so, what happens if an app that has been built to
work with dbus support only (is this even possible?) tries to access jackd
that has no dbus support built-in? If the app has no automatic means of
falling back to the C API access this basically makes jackd as problematic
as the early years of ALSA when apps were unable to work with it because
they only supported OSS... If so, I think this is a *really bad* move. In
addition, is "falling back" aspect of this hypothetical case something that
jack handles automagically or is this an added overhead for a programmer?
Latter, of course, would be yet another *really bad* move IMHO...
Ico
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Received on Mon May 18 20:15:11 2009
This archive was generated by hypermail 2.1.8 : Mon May 18 2009 - 20:15:11 EEST