Viewing 1 replies (of 1 total)
  • Re,

    Thank you for the feedback. Let us first clarify what that option means and you can then tell us if the term “cron” is still the proper way to describe it.

    MailPoet 3 comes with its own implementation of a task-based scheduling mechanism (what’s otherwise commonly known as “cron”). We do not depend on either the native server cron or WordPress cron. To ensure that tasks are scheduled and processed on time, we need a way to constantly run our plugin. Here’s where the “trigger” option comes into play:

    1) When you select a “visitors to your website” option, our plugin runs only when someone visits your site. If there are tasks to process, we start a daemon (background process) that keeps running until all tasks have been processed.

    2) When you select a “MailPoet’s script” option, our plugin starts a daemon that always runs in the background and acts like a “visitor” by accessing your site every 20 seconds. When there are no tasks to process, it just idles.

    With this in mind, do you have a better suggestion as to what we should otherwise be calling this implementation? We’d love to hear it!

    Regards,
    MailPoet Team.

Viewing 1 replies (of 1 total)

The topic ‘Confusing use of (cron)’ is closed to new replies.