I have this patch that expands the start_pool_if_missing logic, allocating a new pool on demand.
If a pool for a certain authority already exists, the checkout process succeed, and the request goes on as always.
In the other case, a new pool is allocated with the opts() passed to the start_pool_if_missing flag.
This code has been working on my services for a while, and without the presumption of being perfect or to address all the open points in the pool management, it can brings an useful improvement to the current implementation.
If you have any objection or suggestion to the implementation, let me know.
Hi @essen!
I have this patch that expands the
start_pool_if_missing
logic, allocating a new pool on demand.If a pool for a certain authority already exists, the checkout process succeed, and the request goes on as always. In the other case, a new pool is allocated with the opts() passed to the
start_pool_if_missing
flag.This code has been working on my services for a while, and without the presumption of being perfect or to address all the open points in the pool management, it can brings an useful improvement to the current implementation.
If you have any objection or suggestion to the implementation, let me know.