#5954 - Be more conservative about the use of extending PHP time limit
| Identifier | #5954 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Be more conservative about the use of extending PHP time limit |
| Status | Open |
| Tags |
Risk: Changes core website behaviour (custom) Roadmap: Over the horizon (custom) Type: Performance (custom) |
| Handling member | Deleted |
| Addon | core |
| Description | As we progress further in time, extending the PHP time limit is becoming more and more a restricted setting in webhosts (for good reason; stability). Furthermore, extending the PHP time limit is mute when one uses a load balancer or proxy which has its own upstream timeout (e.g. Cloudflare, Nginx)... and these technologies are ever-more popular today.
We should consider altering our developer approach. With the exception of Composr release tools, wherever we need to extend the PHP time limit, we should use the refresh technique instead (like we do in the importer), or perhaps AJAX, to step through the process bit by bit. This should be documented in the codebook. On the same note, standardise our method across all systems (except minikernel systems like the installer and upgrader). |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
There have been no comments yet