Support of stream in HTTP request instead of swoole_http_request->rawContent(): string

[ezimuel]

This is actually not an issue but a request for a new feature/improvement.

Right now, we have only swoole_http_request->rawContent(): string function to get the body of a HTTP request. This can be a limit for big data transfer. The proposal is to use stream to manage the HTTP request and response body. Something similar to the PSR-7 Stream here: https://www.php-fig.org/psr/psr-7/#13-streams.

Do you think that this feature can be added to Swoole? Thanks!

[matyhtf]

Your proposal is very good, we have a lot of places to return large strings, we can use stream to avoid copying

[ezimuel]

@matyhtf very cool! Let me know if I can help in any way. Thanks!

[ezimuel]

@matyhtf any news on the proposal of using stream? Thanks!

[Gemorroj]

@matyhtf @twose
any plans for this proposal?

[deminy]

The Swoole team is focusing on code development for the next main release (4.5), which is planned to be released during Chinese New Year (around the end of this month). I won't expect @matyhtf or @twose could have time having this feature added at that time, but I will check with them and see if they could have this included in next few months. Thanks

[embluk]

@deminy Any updates on this feature?

[deminy]

This has been brought to the core development team three times this year, but there is no clear timeline for it yet. In short, it takes tremendous effort to support it in the coroutine server (\Swoole\Coroutine\Server), and there are a few other projects/tasks on the roadmap to finish first. I'd say no earlier than Swoole 5 or Swoole 6.

I'm sorry that it won't be there soon. Please understand that the team has been working hard to make Swoole better and to support the community; unfortunately, there isn't enough time and resources to do everything.

[embluk]

This has been brought to the core development team three times this year, but there is no clear timeline for it yet. In short, it takes tremendous effort to support it in the coroutine server (\Swoole\Coroutine\Server), and there are a few other projects/tasks on the roadmap to finish first. I'd say no earlier than Swoole 5 or Swoole 6.

I'm sorry that it won't be there soon. Please understand that the team has been working hard to make Swoole better and to support the community; unfortunately, there isn't enough time and resources to do everything.

Okay, I understand, thank you for the update!

[qiqizjl]

Is there any progress on this matter? It is very inconvenient to deal with large files at present.

[grayTele]

调用openai接口的stream流式响应输出没有办法逐字即时输出
The stream-style response output from calling the OpenAI interface cannot be outputted instantly on a word-by-word basis.

[binaryfire]

Hi @deminy. Just wondering if this is still planned? Streaming is critical for building apps that integrate with AI provider APIs (OpenAI, Anthropic etc). I think It’s really important for Swoole to support this now that AI integrations are so common.

[Kezino]

First of all, thank you for the amazing work — this is truly a great library and a pleasure to use!

However, this specific issue with the Swoole HTTP client buffering the entire response before delivering it has unfortunately become a bit of a deal breaker for my use case. I’m relying on real-time streaming from OpenAI, and I haven’t found a way to work around this limitation so far.

If anyone has suggestions or ideas on how to overcome this, I’d be really grateful. Thanks again for all the great work on this project!