#3568 Support notification mechanism for KCM caches
Closed: cloned-to-github 2 years ago by pbrezina. Opened 4 years ago by rishi.

Since the KCM caches are implemented by a D-Bus service, it would be good to have a signal that's emitted whenever the caches change. It would be analogous to using inotity watches for FILE or DIR caches.

The lack of a notification API means gnome-online-accounts has to poll the cache every few seconds to keep the GNOME integration in sync. Polling is problematic because it hurts battery consumption. This has already been a problem with KEYRING caches. I hope KCM will make things better.


Metadata Update from @lslebodn:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1511945

4 years ago

Metadata Update from @lslebodn:
- Issue tagged with: KCM

4 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.0
- Issue tagged with: RFE

4 years ago

Metadata Update from @jhrozek:
- Issue priority set to: major

4 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)

2 years ago

Metadata Update from @pbrezina:
- Issue assigned to pbrezina

2 years ago

@pbrezina - should this ticket be merged with https://pagure.io/SSSD/sssd/issue/1497 ? Or is this meant to be a subset of the events generated for #1497?

I'm still in process of identifying what needs to be signaled in order to solve issue from the linked bugzilla. So I will tell for sure once I have all the information, but I see this ticket as a subset of #1497.

Metadata Update from @thalman:
- Issue tagged with: bugzilla

2 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4592

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata