To simplify the usage of Expressive, we added the
run() method, which handles
the incoming request, and emits a response.
The latter aspect, emitting the response, is the responsibility of an emitter. An emitter accepts a response instance, and then does something with it, usually sending the response back to a browser.
The zendframework/zend-httphandlerrunner package defines an
and three emitter implementations. Two of these,
Zend\HttpHandlerRunner\Emitter\SapiStreamEmitter, send headers and output
using PHP's standard SAPI mechanisms (the
header() method and the output
We recognize that there are times when you may want to use alternate emitter implementations; for example, if you use React, the SAPI emitter will likely not work for you.
To facilitate alternate emitters, we offer two facilities:
- First, a
Zend\HttpHandlerRunner\RequestHandlerRunnerinstance is composed in the
Applicationinstance, and you can specify an alternate emitter during instantiation, or via the
Zend\HttpHandlerRunner\Emitter\EmitterInterfaceservice when using the container factory.
- Second, we provide
Zend\HttpHandlerRunner\Emitter\EmitterStack, which allows you to compose multiple emitter strategies; the first to return a boolean true will cause execution of the stack to short-circuit. The
RequestHandlerRunnerservice composes an
EmitterStackby default, with an
SapiEmittercomposed at the bottom of the stack.
Found a mistake or want to contribute to the documentation? Edit this page on GitHub!