You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before the merge of the PR putting request_id's into responses, the connection pool was necessary to ensure correlatable requests & responses (by making a new socket connection for every request) -- now that we have the request IDs we can greatly simplify the correlation logic.
Whether to pool or not (or restrict the pool to some small limit) is up for discussion.
The text was updated successfully, but these errors were encountered:
Before the merge of the PR putting request_id's into responses, the connection pool was necessary to ensure correlatable requests & responses (by making a new socket connection for every request) -- now that we have the request IDs we can greatly simplify the correlation logic.
Whether to pool or not (or restrict the pool to some small limit) is up for discussion.
The text was updated successfully, but these errors were encountered: