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
I've played around with several approaches to a sane streaming API while implementing this via #56:
The response could implement the ReadableStreamInterface. This works out reasonably well for the receiving side through the decorator pattern, but does not really fit for outgoing requests.
The fetch API offers additional methods and requires a custom Response object which still has to implement the base ResponseInterface. This works out reasonably well for the receiving side through the decorator pattern, but does not really fit for outgoing requests.
The fetch API resolves as soon as the headers has been received without waiting for the whole body. This is the main takeaway here.
Activity
clue commentedon Sep 4, 2015
Also take connection hijacking into account for protocols that write outgoing data even after receiving the response headers.
clue commentedon Mar 5, 2016
This feature will likely be resolved with #30. API draft:
clue commentedon Apr 2, 2016
I've played around with several approaches to a sane streaming API while implementing this via #56: