Rename internal SAPI handlers to HttpServerRunner and SapiRunner and update API to use invokable classes
#294
+186
−159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changeset renames the internal SAPI handlers to
HttpServerRunnerandSapiRunnerand updates the API to use invokable classes instead of arun()method. This is mostly done as an internal preparation at the moment, but may be exposed as part of our public API that allows us to reuse this logic for more classes in a follow-up.The goal is to prepare the internal APIs to allow custom application runners, think queue runners, CRON, a FastCGI server and more. Once PSR-15 is fully integrated (see wish list #293), we may decouple this further to use the PSR-15
RequestHandlerAPI. For now, the callable syntax should be good enough.Builds on top of #292, #289, #236, #224, #44, and others