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

List:       freedesktop-dbus
Subject:    Re: Detect new available names in bus
From:       Sergio Costas <rastersoft () gmail ! com>
Date:       2022-02-15 14:15:20
Message-ID: 2e92cbb7-e144-08a7-9a66-0838504e548c () gmail ! com
[Download RAW message or body]


El 15/2/22 a las 14:35, Ralf Habacker escribió:
> Am 15.02.22 um 11:35 schrieb Sergio Costas:
>>
>> El 15/2/22 a las 10:44, Ralf Habacker escribió:
>
>> Which confirms that the dbus daemon is already monitoring those 
>> folders (both with inotify for linux and kqueue for BSD), so adding 
>> that dbus signal sould be quite straightforward...
>>
>> So... How much complex is to submit a proposal for modifying the 
>> specification...?
>>
>
> 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.

-- 
Nos leemos
		         RASTER    (Linux user #228804)
rastersoft@gmail.com                https://www.rastersoft.com

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