Anton Tsitou

@rustatian I think it's a great idea but wonder if it already should be working since the link should be resolved by PHP interpreter at start...

We are going to do something very crazy in 2.0 to solve it.

Redis is already there if you use it as KV storage.

It can be done by locking done and working with one worker within the request. This is definitely something we are going to consider adding going forward.

I have put a foundation for streaming responses into a newer version. Streaming requests will be looked at once this feature it complete. See spiral/roadrunner#9

This will be coming in a separate server due async mode of underlying workers.

Yes, this issue will be reconsidered for 1.5.0. No timeline yet but there are some initial experiments already made.

Not in 1.5.0. We are working on a protocol update (with few extra features and perf improvements), so most likely it will be 2.0.0.

With RR2 refactor we might be able to take a look at this issue with a fresh approach. We will discuss this internally to see if it is possible.

Essentially we have an idea of how to solve this issue with: 1) No memory leaks 2) No blocking on HTTP worker 3) Proper load balancing and prevention of over...