#2329 sbus_get_sender_id_send should chain concurrent request for the same sender
Closed: wontfix 5 years ago Opened 9 years ago by jhrozek.

In the current form, sbus_get_sender_id_send sends a message to the system bus for every unknown sender. We might want to optimize that by chaining the duplicate requests if the previous is still in progress.

As a side note, we do the same for Data Provider lookups, perhaps we should refactor the DP lookups and/or use the same code.


Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred
rhbz: => 0

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

I'm closing this since we have reimplemented sbus in SSSD 2.0 and we do not plan to work on this.

Metadata Update from @pbrezina:
- Custom field design_review reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

5 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/3371

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.

Login to comment on this ticket.

Metadata