Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

implement support for ns_add_io_timeout_job for all event backends #1444

Closed
389-ds-bot opened this issue Sep 12, 2020 · 3 comments
Closed

implement support for ns_add_io_timeout_job for all event backends #1444

389-ds-bot opened this issue Sep 12, 2020 · 3 comments
Labels
closed: duplicate Migration flag - Issue

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48113

  • Created at 2015-03-07 01:06:12 by rmeggins (@richm)
  • Closed as Duplicate
  • Assigned to nobody

For example, tevent does not support timed io events like libevent. Not sure about libev or other event backends.

ns_job_t already has pointers to multiple event fw events:

    ns_event_fw_fd_t *ns_event_fw_fd; /* event framework fd event object */
    ns_event_fw_time_t *ns_event_fw_time; /* event framework timer event object */
    ns_event_fw_sig_t *ns_event_fw_sig; /* event framework signal event object */

ns_add_io_timeout_job could allocate ns_event_fw_fd and ns_event_fw_time, then the event_cb could determine which one of these should be used, and set the job output_type for the actual job callback.

Or, we could push this functionality into ns_event_fw.h - have new ns_event_fw_t functions for ns_event_fw_add_io_timer, ns_event_fw_modify_io_timer, and ns_event_fw_io_timer_event_done

@389-ds-bot 389-ds-bot added the closed: duplicate Migration flag - Issue label Sep 12, 2020
@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2015-03-07 01:39:02

We don't need this right away - 389 uses libevent backend

@389-ds-bot
Copy link
Author

@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2017-02-11 23:09:48

Metadata Update from @richm:

  • Issue set to the milestone: N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: duplicate Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant