On Fri, Jan 08, 2010 at 01:02:55PM +0000, Chris Cannam wrote:
> For my part (and I realise I'm probably inviting the wrath of Fons and
> others here) I'd probably rather add some D-BUS or equivalent "proper"
> message receipt to the application and be done with it.
You may be mistaken here :-). IMHO a D-BUS message would be
much cleaner than hijacking SIGUSR1...
The thing that could 'invite my wrath' is of a different
nature:
- In a first stage, corners are cut in order to minimize
the changes required to exising apps and invite early
adoption.
- Some time later the half-baked solutions resulting from
this are cast into stone in the interest of 'backward
compatibility'.
This sort of scenario is fairly typical and IMHO it is not
a Good Thing (TM).
If an app has to perform well in a managed environment it
has to be designed for this, just as it has to be designed
to be a good Jack client. There's nothing difficult about
this, and no deep mysteries are involved. It just requires
some thinking, time and effort. Trying to skip this will
just result in more misery later, just as writing Jack apps
that are not RT-safe - once they are finished it's usually
quite difficult to modify them.
Ciao,
-- FA _______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@email-addr-hidden http://lists.linuxaudio.org/listinfo/linux-audio-devReceived on Sat Jan 9 16:15:02 2010
This archive was generated by hypermail 2.1.8 : Sat Jan 09 2010 - 16:15:02 EET