You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 29, 2020. It is now read-only.
Removes output buffer awareness from Server, emitters
By removing a call to `ob_start()` within `Server::listen()`, we can
solve the issue of detecting when we have both a response and content in
the output buffer; in most cases, we will have already sent headers,
which will cause an exception to be raised; we can also check the
_current_ output buffer and, if non-empty, raise an exception.
This means we can:
- Remove the `SapiEmitterTrait::flush()` implementation, and all calls
to it.
- Remove the `$maxBufferLevel` argument to each emitter.
- Remove tests regarding interactions of emitters with the output buffer.
This is a backwards-incompatible change. However, it fixes a rather
tricky problem that occurs currently when mixing buffered output and
response instances.
0 commit comments