Absence of connection pool in object server for sending requests to container server

[Abolfazl Shafiei Marji]

In Swift, the communication between the proxy server and the object server is typically handled using the Swift client library that provides connection pooling functionality for reusing existing connections to the object servers. But for the communication between the object server and the container server, Each request to the container server is typically a separate HTTP connection established and closed by the object server. I think Considering the limitation of the operating system's port number and the overhead of creating new connections for each request, this isn't a good idea. Please explain if there is a specific reason for this implementation. thanks