Why discuz This feature scheduling task function without event scheduling?

I went to the designated time to observe the database found that the specified data has not changed, that is, the scheduled task is not executed, I heard that the open page to execute, I took it why the team does not use event scheduling?

Reply content:

I went to the designated time to observe the database found that the specified data has not changed, that is, the scheduled task is not executed, I heard that the open page to execute, I took it why the team does not use event scheduling?

You are two questions:

1. Discuz didn't perform the scheduled task.

2. Discuz's development team does not use event scheduling

The first question, it should be said that if your site does not have any user access, it is possible to really do not execute, after all, Discuz's scheduled task is to trigger execution. As to how to solve, it is recommended to look for a post like this, there may be upgrade or plug-in caused by the installation.

The second question, should be the design of the discuz decision, I guess it is the design of the idea is to use the most basic PHP and MySQL can complete the main functions, so the design time did not consider using event scheduling.

Because he has to think about the space that the user is using

Virtual hosts do not have crontab permissions, and technology has always been a trade-off in terms of constraints.
This function I think may be:
Write the configuration to a randomly named file, and then PHP ignores the user shutdown, the dead loop runs to the point of execution, and if the configuration file does not exist, exit.

