[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-dbus
Subject:    Re: Detect new available names in bus
From:       Ralf Habacker <ralf.habacker () freenet ! de>
Date:       2022-02-16 8:54:45
Message-ID: 89ce1ca1-4561-aade-ed95-602f00f31868 () freenet ! de
[Download RAW message or body]

Am 15.02.22 um 15:15 schrieb Sergio Costas:
> 
>> This depends on what kind of signal is required.
>>
>> Thiago stated that you can get the present available names on the bus 
>> by running.
>>
>> > $ qdbus org.freedesktop.DBus / ListActivatableNames
>>
>> If this suits your needs, a new signal with no other parameters would 
>> suffice, telling that the configuration has been reloaded.
>>
>> In that case an additional section in the spec like 
>> https://gitlab.freedesktop.org/dbus/dbus/-/blob/master/doc/dbus-specification.xml#L6378 
>> would do it.
>>
>> The new implementation needs to be added to 
>> bus_context_reload_config() (see 
>> https://gitlab.freedesktop.org/dbus/dbus/-/blob/master/bus/bus.c#L1079)
>>
>> As example for constructing and sending a signal, see 
>> https://gitlab.freedesktop.org/dbus/dbus/-/blob/master/bus/driver.c#L340
>>
>>
> Thanks! I'll check all that.
> 
Simon McVittie and I once agreed on a suitable implementation for this, 
see https://gitlab.freedesktop.org/dbus/dbus/-/merge_requests/250. It 
would be helpful if you would create a corresponding feature request 
https://gitlab.freedesktop.org/dbus/dbus/-/issues/new?issue%5Bmilestone_id%5D= 
for this.

Ralf
[prev in list] [next in list] [prev in thread] [next in thread]