Hello, thanks for proposing. Can you explain your use case?
The AsyncDecoratorTrait + AsyncResponse combo is a way better alternative to me since it also works with $client->stream(), while simple response decorators don't.

Hi @nicolas-grekas, thanks for your feedback. I took the opportunity to take a deeper look at the AsyncResponse concept. It looks really nice. I was able to do almost everything I wanted to do with response wrappers.

My last use case is a caching client decorator. Same as the internal CachingHttpClient, but with a custom cache solution instead of HttpCache. We need to add extra headers to the cached response (age, ID, etc.). So we created a wrapper for the response and decorate the getHeaders() method.
With the AsyncResponse, I was able to modify the content of the original response (by yielding extra chunks in the passthru), but not the other information (status code, headers and debug infos). Do you know how I can do that ?

I saw that the AsyncContext has a replaceResponse() method. But it seems a bit overkill to recreate an entire response. And the method seem to be designed to return the result of a second HTTP request, not overwrite the first one. Maybe adding replaceResponseHeaders() and replaceResponseInfo() methods to AsyncContext will do the trick ? What do you think ?

I don't know if it worth it, but I added a static stream() method to the DecoratorTrait to make it work with $client->stream().