Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Currently, users must use the static PoolManager class to create and lookup Pools on the client side. This is problematic for several reasons:
1. PoolManager is hard to mock because it consists of static methods
2. Being a static singleton with state, PoolManager locks the client into only having one PoolManager and associated ClientCache.
3. The lifecycle of Pools in the PoolManager is strange, they can be created before or after the ClientCache, but they are destroyed when the ClientCache is destroyed.
Attachments
Issue Links
- supercedes
-
GEODE-7532 PoolManagerImpl.register(:Pool) and PoolManagerImpl.unregister(:Pool) should be declared on the PoolManager interface
- Resolved