Potential Issue with Simultaneous Requests Using a Single HTTP Client Instance

[skydiablo]

Hi ReactPHP community,
I’m working on an application that uses the ReactPHP HTTP client to send multiple simultaneous requests to a CrateDB server (via its HTTP JSON API). I’m using a single HTTP client instance for all requests throughout the application’s lifecycle, leveraging ReactPHP’s async capabilities.
Observed Issue
After processing, I’ve noticed that some of the data stored in CrateDB appears corrupted. This corruption seems to occur when multiple requests are sent simultaneously using the same client instance. My hypothesis is that this might be related to:

TCP packet interleaving on the same connection (e.g., if requests/responses overlap or are processed out of order).
Connection caching/keep-alive behavior in ClientConnectionManager::connect and ClientConnectionManager::keepAlive.
Key Questions

Can simultaneous requests using the same client instance interfere with each other at the TCP/HTTP layer, especially when using HTTP/1.1 with keep-alive? Could this lead to data corruption on the server side?
Could the connection caching/keep-alive logic in ClientConnectionManager contribute to this issue? For example, if connections are reused improperly or requests/responses are misrouted.
Best practices for isolation:

Should I create a new client instance per request to guarantee isolation (at the cost of performance)?
Would a connection pool (or disabling keep-alive) be a better solution?

I’d love to hear from the community:

• Are there known pitfalls with reusing a single client instance for concurrent requests?
• Are there recommended patterns for handling high concurrency with ReactPHP’s HTTP client to avoid data corruption?

Thanks in advance for your insights!
Volker

[skydiablo]

okay, nevermind, the react HTTP client implementation is bullet proof! thx for attention!