The libjackconfig thread fork (Was: Server control plug-ins proposal)

> Le 3 juin 09 à 20:27, torbenh@... a écrit :
>
>> On Wed, Jun 03, 2009 at 05:03:15PM +0200, Stéphane Letz wrote:
>>> Knows problems, limitations:
>>> =======================
>>>
>>> - since the DBus code (now in "jack_control_dbus") uses it's own  
>>> server
>>> setting format (XML file), they are still state coherency issues  
>>> between
>>> the state kept in this XML file and the state used by the running  
>>> server. A
>>> possible solution would be for the "jack_control_dbus" plug-in to  
>>> get the
>>> state from the running server and save it in it's own format. But  
>>> Nedko can
>>> comment more on that specific point.
>>
>> if we find out how to prevent plugin config fighting, the plugin could
>> configure the server_ctl before its started.
>>
>> is the libjackconfig idea still in discussion ?
>
> Yes, I think we should now works on libjackconfig idea. We could have  
> the following stategy:
>
> 1) jackd started with parameters ==> those parameters are used, and  
> saved as a so called "default" state using libjackconfig
>
> 3) jacks started without parameters ==> any control plug-in should  
> load the so called "default" state using libjackconfig and configure  
> the server with it.