On Fr, 10.04.20 12:06, David J (ema...@icloud.com) wrote:
> Giacinto,
> Thanks for further explaining my email.
>
> Lennart,
> Thank you for your feedback. What I am doing is writing an sd-bus
> interface and a client code, which is only interested in specific
> signal information. So the interfa
Giacinto,
Thanks for further explaining my email.
Lennart,
Thank you for your feedback. What I am doing is writing an sd-bus interface and
a client code, which is only interested in specific signal information. So the
interface has to offer minimal API’s. The interface has one callback to handl
hi Lennart,
On Fri, Apr 10, 2020 at 2:14 PM Lennart Poettering
wrote:
>
> On Do, 09.04.20 14:12, David J (ema...@icloud.com) wrote:
>
> > Hello Systemd developers!
> >
> > > I asked this question earlier but I haven’t gotten any reply so I thought
> > > asking again.
> >
> > > Question regarding
On Do, 09.04.20 14:12, David J (ema...@icloud.com) wrote:
> Hello Systemd developers!
>
> > I asked this question earlier but I haven’t gotten any reply so I thought
> > asking again.
>
> > Question regarding sd_bus_add_match (sd-bus.c):
> >
> > Is there any bad consequences to use the same callb
Hello Systemd developers!
> I asked this question earlier but I haven’t gotten any reply so I thought
> asking again.
> Question regarding sd_bus_add_match (sd-bus.c):
>
> Is there any bad consequences to use the same callback for multiple signal
> match and then using the userdata parameter t
Question regarding sd_bus_add_match (sd-bus.c):
Is it acceptable (or recommended) to use the same callback for multiple signal
match and then using the userdata parameter to distinguish among the different
signals? See the sample code below for a reference of what I am trying to do.
/*Begi
