Why does discuz not need to schedule tasks?

When I arrived at the specified time, I observed that the specified data had not changed, that is, the scheduled task was not executed. I heard that the task was executed only when the page was opened. Why didn't the team use event scheduling?

When I arrived at the specified time, I observed that the specified data had not changed, that is, the scheduled task was not executed. I heard that the task was executed only when the page was opened. Why didn't the team use event scheduling?

Reply content:

When I arrived at the specified time, I observed that the specified data had not changed, that is, the scheduled task was not executed. I heard that the task was executed only when the page was opened. Why didn't the team use event scheduling?

You have two questions:

1. Discuz does not execute the scheduled task

2. The Discuz development team does not need to schedule events.

First, it should be said that if your website is not accessed by any user, it may indeed not be executed. after all, Discuz's scheduled tasks are triggered. As for how to solve the problem, we suggest you look for a post like this, which may be caused by upgrades or plug-ins.

The second question should be determined by the design idea of Discuz. I guess its design idea is to use the most basic php and mysql to complete the main functions, therefore, event scheduling is not considered during the design.

Because he wants to consider that the user uses space.

The virtual host does not have the crontab permission, and the technology has always been weighed under restrictions.
I think this function may be:
Write the configuration to a randomly named file, and then php ignores the user's shutdown. the endless loop runs until it reaches the dot. if the configuration file does not exist, it exits.