#4714 - Persistent app server support

Identifier #4714
Issue type Feature request or suggestion
Title Persistent app server support
Status Open
Tags

Risk: Major rearchitecting (custom)

Type: Cross-cutting feature (custom)

Type: Performance (custom)

Handling member Deleted
Addon core
Description There is an interesting discussion over at Drupal about supporting persistent app servers:
https://www.drupal.org/project/drupal/issues/2218651

In theory it would be a huge improvement.

It also is, however, pretty antithetical to how PHP and Composr (and to some degree Drupal) is designed. For it to work we'd have to vet every part of Composr to not have globals, static cached data in many cases, singletons, static classes. We've used a lot of that stuff to make Composr faster on a normal PHP server. It'd have to be done VERY carefully to avoid security holes in assumptions about what was valid for one request being also valid for the next. The amount of OOP overhead needed would be massive, and generally an enormous project. Doing those changes would make many people happy of course. And that overhead wouldn't matter as much for a persistent app server as most of the cost would only happen during initial boost.

Really it would be making PHP a lot more like a Java web server, with an entirely different set of tradeoffs.

I doubt there would ever be enough resources to make this all happen, but you never know, so I want this issue to stay here.
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".

Rating

Unrated