View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005954 | Composr | core | public | 2024-09-19 16:58 | 2024-09-26 10:11 |
| Reporter | Patrick Schmalstig | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0005954: Be more conservative about the use of extending PHP time limit | ||||
| 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). | ||||
| Tags | Risk: Changes core website behaviour, Roadmap: Over the horizon, Type: Performance | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-09-19 16:58 | Patrick Schmalstig | New Issue | |
| 2024-09-19 16:58 | Patrick Schmalstig | Tag Attached: Risk: Changes core website behaviour | |
| 2024-09-19 16:58 | Patrick Schmalstig | Tag Attached: Roadmap: Over the horizon | |
| 2024-09-19 16:58 | Patrick Schmalstig | Tag Attached: Type: Performance | |
| 2024-09-19 17:00 | Patrick Schmalstig | Description Updated | View Revisions |
