Support for client tracking

[lechndo]

Hi guys,

first I want to thank you all for this cool new DBus lib.

I just started an evaluation to to see if the lib fits our needs and after a minor issue with Unix FD support I came across another use case that is essential for us:
Client Tracking
From what I've seen this seems not to be supported by sdbus-cpp but seems to be in the underlying sdbus lib (via sd_bus_track_add_sender etc.).

Is there a way for doing such things in sdbus-cpp that I missed or if it's not is there a plan for adding such functionality?

Thank you in advance...

[sangelovic]

Hi, thanks for kind words. Regarding the unix fd issue, I plan to look into it soon, this got stale somehow. As for the client tracking feature, sdbus-c++ doesn't support that currently (we did not need that), but I don't see any problem with its introduction into the lib. sd-bus provides API for it, so that's fine. I'm however not familiar with this feature. What is it about? Could you provide some more info on it? You can also help out with the implementation if you'd like. Stanislav

…

On Mon, Jun 3, 2019, 09:00 lechndo ***@***.***> wrote: Hi guys, first I want to thank you all for this cool new DBus lib. I just started an evaluation to to see if the lib fits our needs and after a minor issue with Unix FD support I came across another use case that is essential for us: Client Tracking From what I've seen this seems not to be supported by sdbus-cpp but seems to be in the underlying sdbus lib (via sd_bus_track_add_sender etc.). Is there a way for doing such things in sdbus-cpp that I missed or if it's not is there a plan for adding such functionality? Thank you in advance... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#57?email_source=notifications&email_token=ABM3OUWVUNYOJ3H77HUXZYDPYS6PHA5CNFSM4HSFER2KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GXGUE4A>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABM3OUWF2LPXOZW2M2ZMRR3PYS6PHANCNFSM4HSFER2A> .

[lechndo]

Thx for the quick reply.

Unfortunately I'm not yet familiar with the underlying sd-bus lib. I just had a quick look on the functions in sd-bus.h and saw the functions for setting up some kind of message sender tracking.
But I will continue digging...

We previously used dbus-c++ lib and there we just got the messages sender name and then set up a match expression for it to detect when the owner disappears from the bus.
To be able switch to sdbus-c++ we need some similar way for tracking nodes that invoked some special locking methods to be able to automatically release the locks when the node dies.

For sure it will be possible to add such a feature on our own and contribute it back.
I just wanted to make sure that I didn't miss some existing way for doing such things.

Thx for now.
Maybe I'll be back in the future with further questions or points for a discussion or even better with a suggestions for a working implementation. 😁

[lechndo]

Hi guys,
I started playing around with fetching sender name to get more familiar with stuff required for sender tracking.

Could someone please tell me if my approach might be a problem in multi threaded environments or in other situations (e.g. DBus calls executed during method or signal processing).

I want to avoid design flaws but at the moment I have absolutely no idea which things might be a problem in case of multiple threads.

0001-Add-methods-for-fetching-sender-of-current-message.zip

Thx in advance...